You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason Dillon <ja...@planet57.com> on 2007/04/02 22:32:08 UTC
maven-install-plugin :: Cannot override read-only parameter: artifactId ?
I all of a sudden started to see this today:
<snip>
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error configuring: org.apache.maven.plugins:maven-install-
plugin. Reason: ERROR: Cannot override read-only parameter:
artifactId in goal: install:install-file
</snip>
From what I can tell this is using maven-install-plugin 2.1.
Anyone know whats going on? I get the same problem with Maven 2.0.5
and 2.0.6 :-(
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter:
artifactId ?
Posted by jbonevich <jb...@compendiabio.com>.
Some more details on this:
I have a common build project containing only a pom.xml, and several
projects parallel to it with code, etc. and their pom.xmls. No inheritance
involved. Just <module> references in the common build project to the
others. I have a pluginManagement section in the common one that declares
the version of the install plugin as the 2.2-SNAPSHOT. I know this should
not affect the other projects, but I figgered what the heck. I only
explicitly declare use of the 2.2-SNAPSHOT in two of the projects; there are
a couple others that rely on the defaults.
So strangely enough, if I explicitly add a plugins section to one of the
projects that relied on the defaults and declare 2.2-SNAPSHOT as the version
to use, it works on linux now. Must be some weird build ordering thing.
This is really jenky and bad smelling folks.
Anywho, problem solved for now. But you may want to look into this further,
as I can imagine the pain others might be suffering.
jeff
jbonevich wrote:
>
> There is a new wrinkle in this one. The new SNAPSHOT works fine in our
> Windows development environment. However, when we try to run our build on
> our Linux (RHEL) build machine, it only works the first time after
> downloading the install plugin. Every subsequent time fails with the
> "Cannot override read-only parameter" failure. If I blow away the plugin
> in the repository, works fine again the first time. Fails every
> subsequent time. This is really annoying. Anyone else experience this in
> a linux environment?
>
>
>
--
View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10421300
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter:
artifactId ?
Posted by jbonevich <jb...@compendiabio.com>.
There is a new wrinkle in this one. The new SNAPSHOT works fine in our
Windows development environment. However, when we try to run our build on
our Linux (RHEL) build machine, it only works the first time after
downloading the install plugin. Every subsequent time fails with the
"Cannot override read-only parameter" failure. If I blow away the plugin in
the repository, works fine again the first time. Fails every subsequent
time. This is really annoying. Anyone else experience this in a linux
environment?
--
View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10420653
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Stephane Nicoll <st...@gmail.com>.
np :)
There's a couple of issues before we can release it though.
Cheers,
Stéphane
On 5/1/07, Vincent Siveton <vi...@gmail.com> wrote:
> Hi Stephane,
>
> Thanks for this!
> FYI, we need the 2.2 for the ant plugin release.
>
> Cheers,
>
> Vincent
>
> 2007/5/1, Stephane Nicoll <st...@gmail.com>:
> > On 5/1/07, jbonevich <jb...@compendiabio.com> wrote:
> > >
> > > I can confirm that a download of the source from svn and building a snapshot
> > > locally does the trick.
> > >
> > > Please, oh, please, maven-lords that be! Please, deploy a new snapshot of
> > > 2.2 - the one on the snapshot site is almost a year old now. Thanx!
> >
> > Done. We can also release it if there is no more pending issues. I'll
> > have a look.
> >
> > Cheers,
> > Stéphane
> > >
> > > jeff
> > >
> > >
> > >
> > > Jason Dillon wrote:
> > > >
> > > > Aighty I figured this out... the tag for maven-install-plugin-2.1 has
> > > > groupId, artifactId, version, packaging and file all marked with
> > > > '@readonly'. The latest trunk of maven-install-plugin does not have
> > > > these tags.
> > > >
> > > > So, with 2.1 you can only `mvn install:install-file` from the command-
> > > > line, and can not use the install-file goal from an execution.
> > > >
> > > > We need to get 2.2 released.
> > > >
> > > > * * *
> > > >
> > > > This worked for me before because I had built 2.2-SNAPSHOT locally
> > > > (to test my forceVersion patch) and mvn decided to pick that up...
> > > > not sure why though. Why would mvn pick up a locally built SNAPSHOT
> > > > and use that instead of the released 2.1? I don't like the magical
> > > > RELEASE stuff anyways... but I'd not expect that when a <version> for
> > > > a plugin is omitted that mvn would pick up a non-release to use
> > > > instead if it finds one in my repo cache.
> > > >
> > > > --jason
> > > >
> > > >
> > > > On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> > > >
> > > >> I thought that had always been the case and was a known issue in
> > > >> the install plugin.
> > > >>
> > > >> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
> > > >>
> > > >>> I all of a sudden started to see this today:
> > > >>>
> > > >>> <snip>
> > > >>> [INFO]
> > > >>> ---------------------------------------------------------------------
> > > >>> ---
> > > >>> [ERROR] BUILD ERROR
> > > >>> [INFO]
> > > >>> ---------------------------------------------------------------------
> > > >>> ---
> > > >>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
> > > >>> plugin. Reason: ERROR: Cannot override read-only parameter:
> > > >>> artifactId in goal: install:install-file
> > > >>> </snip>
> > > >>>
> > > >>> From what I can tell this is using maven-install-plugin 2.1.
> > > >>>
> > > >>> Anyone know whats going on? I get the same problem with Maven
> > > >>> 2.0.5 and 2.0.6 :-(
> > > >>>
> > > >>> --jason
> > > >>>
> > > >>> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > > --
> > > View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10263145
> > > Sent from the Maven Developers mailing list archive at Nabble.com.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Stephane,
Thanks for this!
FYI, we need the 2.2 for the ant plugin release.
Cheers,
Vincent
2007/5/1, Stephane Nicoll <st...@gmail.com>:
> On 5/1/07, jbonevich <jb...@compendiabio.com> wrote:
> >
> > I can confirm that a download of the source from svn and building a snapshot
> > locally does the trick.
> >
> > Please, oh, please, maven-lords that be! Please, deploy a new snapshot of
> > 2.2 - the one on the snapshot site is almost a year old now. Thanx!
>
> Done. We can also release it if there is no more pending issues. I'll
> have a look.
>
> Cheers,
> Stéphane
> >
> > jeff
> >
> >
> >
> > Jason Dillon wrote:
> > >
> > > Aighty I figured this out... the tag for maven-install-plugin-2.1 has
> > > groupId, artifactId, version, packaging and file all marked with
> > > '@readonly'. The latest trunk of maven-install-plugin does not have
> > > these tags.
> > >
> > > So, with 2.1 you can only `mvn install:install-file` from the command-
> > > line, and can not use the install-file goal from an execution.
> > >
> > > We need to get 2.2 released.
> > >
> > > * * *
> > >
> > > This worked for me before because I had built 2.2-SNAPSHOT locally
> > > (to test my forceVersion patch) and mvn decided to pick that up...
> > > not sure why though. Why would mvn pick up a locally built SNAPSHOT
> > > and use that instead of the released 2.1? I don't like the magical
> > > RELEASE stuff anyways... but I'd not expect that when a <version> for
> > > a plugin is omitted that mvn would pick up a non-release to use
> > > instead if it finds one in my repo cache.
> > >
> > > --jason
> > >
> > >
> > > On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> > >
> > >> I thought that had always been the case and was a known issue in
> > >> the install plugin.
> > >>
> > >> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
> > >>
> > >>> I all of a sudden started to see this today:
> > >>>
> > >>> <snip>
> > >>> [INFO]
> > >>> ---------------------------------------------------------------------
> > >>> ---
> > >>> [ERROR] BUILD ERROR
> > >>> [INFO]
> > >>> ---------------------------------------------------------------------
> > >>> ---
> > >>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
> > >>> plugin. Reason: ERROR: Cannot override read-only parameter:
> > >>> artifactId in goal: install:install-file
> > >>> </snip>
> > >>>
> > >>> From what I can tell this is using maven-install-plugin 2.1.
> > >>>
> > >>> Anyone know whats going on? I get the same problem with Maven
> > >>> 2.0.5 and 2.0.6 :-(
> > >>>
> > >>> --jason
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> > >
> >
> > --
> > View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10263145
> > Sent from the Maven Developers mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Stephane Nicoll <st...@gmail.com>.
On 5/1/07, jbonevich <jb...@compendiabio.com> wrote:
>
> I can confirm that a download of the source from svn and building a snapshot
> locally does the trick.
>
> Please, oh, please, maven-lords that be! Please, deploy a new snapshot of
> 2.2 - the one on the snapshot site is almost a year old now. Thanx!
Done. We can also release it if there is no more pending issues. I'll
have a look.
Cheers,
Stéphane
>
> jeff
>
>
>
> Jason Dillon wrote:
> >
> > Aighty I figured this out... the tag for maven-install-plugin-2.1 has
> > groupId, artifactId, version, packaging and file all marked with
> > '@readonly'. The latest trunk of maven-install-plugin does not have
> > these tags.
> >
> > So, with 2.1 you can only `mvn install:install-file` from the command-
> > line, and can not use the install-file goal from an execution.
> >
> > We need to get 2.2 released.
> >
> > * * *
> >
> > This worked for me before because I had built 2.2-SNAPSHOT locally
> > (to test my forceVersion patch) and mvn decided to pick that up...
> > not sure why though. Why would mvn pick up a locally built SNAPSHOT
> > and use that instead of the released 2.1? I don't like the magical
> > RELEASE stuff anyways... but I'd not expect that when a <version> for
> > a plugin is omitted that mvn would pick up a non-release to use
> > instead if it finds one in my repo cache.
> >
> > --jason
> >
> >
> > On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> >
> >> I thought that had always been the case and was a known issue in
> >> the install plugin.
> >>
> >> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
> >>
> >>> I all of a sudden started to see this today:
> >>>
> >>> <snip>
> >>> [INFO]
> >>> ---------------------------------------------------------------------
> >>> ---
> >>> [ERROR] BUILD ERROR
> >>> [INFO]
> >>> ---------------------------------------------------------------------
> >>> ---
> >>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
> >>> plugin. Reason: ERROR: Cannot override read-only parameter:
> >>> artifactId in goal: install:install-file
> >>> </snip>
> >>>
> >>> From what I can tell this is using maven-install-plugin 2.1.
> >>>
> >>> Anyone know whats going on? I get the same problem with Maven
> >>> 2.0.5 and 2.0.6 :-(
> >>>
> >>> --jason
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10263145
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter:
artifactId ?
Posted by jbonevich <jb...@compendiabio.com>.
I can confirm that a download of the source from svn and building a snapshot
locally does the trick.
Please, oh, please, maven-lords that be! Please, deploy a new snapshot of
2.2 - the one on the snapshot site is almost a year old now. Thanx!
jeff
Jason Dillon wrote:
>
> Aighty I figured this out... the tag for maven-install-plugin-2.1 has
> groupId, artifactId, version, packaging and file all marked with
> '@readonly'. The latest trunk of maven-install-plugin does not have
> these tags.
>
> So, with 2.1 you can only `mvn install:install-file` from the command-
> line, and can not use the install-file goal from an execution.
>
> We need to get 2.2 released.
>
> * * *
>
> This worked for me before because I had built 2.2-SNAPSHOT locally
> (to test my forceVersion patch) and mvn decided to pick that up...
> not sure why though. Why would mvn pick up a locally built SNAPSHOT
> and use that instead of the released 2.1? I don't like the magical
> RELEASE stuff anyways... but I'd not expect that when a <version> for
> a plugin is omitted that mvn would pick up a non-release to use
> instead if it finds one in my repo cache.
>
> --jason
>
>
> On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
>
>> I thought that had always been the case and was a known issue in
>> the install plugin.
>>
>> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
>>
>>> I all of a sudden started to see this today:
>>>
>>> <snip>
>>> [INFO]
>>> ---------------------------------------------------------------------
>>> ---
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ---------------------------------------------------------------------
>>> ---
>>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
>>> plugin. Reason: ERROR: Cannot override read-only parameter:
>>> artifactId in goal: install:install-file
>>> </snip>
>>>
>>> From what I can tell this is using maven-install-plugin 2.1.
>>>
>>> Anyone know whats going on? I get the same problem with Maven
>>> 2.0.5 and 2.0.6 :-(
>>>
>>> --jason
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10263145
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Jason Dillon <ja...@planet57.com>.
Aighty I figured this out... the tag for maven-install-plugin-2.1 has
groupId, artifactId, version, packaging and file all marked with
'@readonly'. The latest trunk of maven-install-plugin does not have
these tags.
So, with 2.1 you can only `mvn install:install-file` from the command-
line, and can not use the install-file goal from an execution.
We need to get 2.2 released.
* * *
This worked for me before because I had built 2.2-SNAPSHOT locally
(to test my forceVersion patch) and mvn decided to pick that up...
not sure why though. Why would mvn pick up a locally built SNAPSHOT
and use that instead of the released 2.1? I don't like the magical
RELEASE stuff anyways... but I'd not expect that when a <version> for
a plugin is omitted that mvn would pick up a non-release to use
instead if it finds one in my repo cache.
--jason
On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> I thought that had always been the case and was a known issue in
> the install plugin.
>
> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
>
>> I all of a sudden started to see this today:
>>
>> <snip>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
>> plugin. Reason: ERROR: Cannot override read-only parameter:
>> artifactId in goal: install:install-file
>> </snip>
>>
>> From what I can tell this is using maven-install-plugin 2.1.
>>
>> Anyone know whats going on? I get the same problem with Maven
>> 2.0.5 and 2.0.6 :-(
>>
>> --jason
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Raphaël Piéroni <ra...@gmail.com>.
Hi Jason,
My problem was the usage of properties $(project.version} ${project.groupId}
in the depMan of the parent pom. I now enforce manual resolution.
The depMan defined the modules version and groupId for other modules.
Regards,
Raphaël
2007/4/3, Jason Dillon <ja...@planet57.com>:
> I had this working for a while... maybe I changed something in the
> plugin locally... will look at it again, I need this to work for my
> integration test muck.
>
> --jason
>
>
> On Apr 2, 2007, at 7:59 PM, Brian E. Fox wrote:
>
> > Rahul was having this problem with the achetypeNG with groupId, even
> > though the original archetype didn't have this problem. I seem to
> > recall
> > he figured it out, but not the solution.
> >
> > -----Original Message-----
> > From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
> > Dillon
> > Sent: Monday, April 02, 2007 8:11 PM
> > To: Maven Developers List
> > Subject: Re: maven-install-plugin :: Cannot override read-only
> > parameter: artifactId ?
> >
> > It was working for me for a while... then it stopped. I don't know
> > why at all. This is install:install-file, not install:install, so
> > you are expected to configure the artifactId. Its not marked as read-
> > only. But I've not idea why it just started complaining to me about
> > it...
> >
> > :-(
> >
> > --jason
> >
> >
> > On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> >
> >> I thought that had always been the case and was a known issue in
> >> the install plugin.
> >>
> >> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
> >>
> >>> I all of a sudden started to see this today:
> >>>
> >>> <snip>
> >>> [INFO]
> >>> --------------------------------------------------------------------
> >>> -
> >
> >>> ---
> >>> [ERROR] BUILD ERROR
> >>> [INFO]
> >>> --------------------------------------------------------------------
> >>> -
> >
> >>> ---
> >>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
> >>> plugin. Reason: ERROR: Cannot override read-only parameter:
> >>> artifactId in goal: install:install-file
> >>> </snip>
> >>>
> >>> From what I can tell this is using maven-install-plugin 2.1.
> >>>
> >>> Anyone know whats going on? I get the same problem with Maven
> >>> 2.0.5 and 2.0.6 :-(
> >>>
> >>> --jason
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Jason Dillon <ja...@planet57.com>.
I had this working for a while... maybe I changed something in the
plugin locally... will look at it again, I need this to work for my
integration test muck.
--jason
On Apr 2, 2007, at 7:59 PM, Brian E. Fox wrote:
> Rahul was having this problem with the achetypeNG with groupId, even
> though the original archetype didn't have this problem. I seem to
> recall
> he figured it out, but not the solution.
>
> -----Original Message-----
> From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
> Dillon
> Sent: Monday, April 02, 2007 8:11 PM
> To: Maven Developers List
> Subject: Re: maven-install-plugin :: Cannot override read-only
> parameter: artifactId ?
>
> It was working for me for a while... then it stopped. I don't know
> why at all. This is install:install-file, not install:install, so
> you are expected to configure the artifactId. Its not marked as read-
> only. But I've not idea why it just started complaining to me about
> it...
>
> :-(
>
> --jason
>
>
> On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
>
>> I thought that had always been the case and was a known issue in
>> the install plugin.
>>
>> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
>>
>>> I all of a sudden started to see this today:
>>>
>>> <snip>
>>> [INFO]
>>> --------------------------------------------------------------------
>>> -
>
>>> ---
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> --------------------------------------------------------------------
>>> -
>
>>> ---
>>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
>>> plugin. Reason: ERROR: Cannot override read-only parameter:
>>> artifactId in goal: install:install-file
>>> </snip>
>>>
>>> From what I can tell this is using maven-install-plugin 2.1.
>>>
>>> Anyone know whats going on? I get the same problem with Maven
>>> 2.0.5 and 2.0.6 :-(
>>>
>>> --jason
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Rahul was having this problem with the achetypeNG with groupId, even
though the original archetype didn't have this problem. I seem to recall
he figured it out, but not the solution.
-----Original Message-----
From: Jason Dillon [mailto:jason.dillon@gmail.com] On Behalf Of Jason
Dillon
Sent: Monday, April 02, 2007 8:11 PM
To: Maven Developers List
Subject: Re: maven-install-plugin :: Cannot override read-only
parameter: artifactId ?
It was working for me for a while... then it stopped. I don't know
why at all. This is install:install-file, not install:install, so
you are expected to configure the artifactId. Its not marked as read-
only. But I've not idea why it just started complaining to me about
it...
:-(
--jason
On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> I thought that had always been the case and was a known issue in
> the install plugin.
>
> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
>
>> I all of a sudden started to see this today:
>>
>> <snip>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
>> plugin. Reason: ERROR: Cannot override read-only parameter:
>> artifactId in goal: install:install-file
>> </snip>
>>
>> From what I can tell this is using maven-install-plugin 2.1.
>>
>> Anyone know whats going on? I get the same problem with Maven
>> 2.0.5 and 2.0.6 :-(
>>
>> --jason
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Jason Dillon <ja...@planet57.com>.
It was working for me for a while... then it stopped. I don't know
why at all. This is install:install-file, not install:install, so
you are expected to configure the artifactId. Its not marked as read-
only. But I've not idea why it just started complaining to me about
it...
:-(
--jason
On Apr 2, 2007, at 4:44 PM, Brett Porter wrote:
> I thought that had always been the case and was a known issue in
> the install plugin.
>
> On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
>
>> I all of a sudden started to see this today:
>>
>> <snip>
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [ERROR] BUILD ERROR
>> [INFO]
>> ---------------------------------------------------------------------
>> ---
>> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
>> plugin. Reason: ERROR: Cannot override read-only parameter:
>> artifactId in goal: install:install-file
>> </snip>
>>
>> From what I can tell this is using maven-install-plugin 2.1.
>>
>> Anyone know whats going on? I get the same problem with Maven
>> 2.0.5 and 2.0.6 :-(
>>
>> --jason
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
Posted by Brett Porter <br...@apache.org>.
I thought that had always been the case and was a known issue in the
install plugin.
On 03/04/2007, at 6:32 AM, Jason Dillon wrote:
> I all of a sudden started to see this today:
>
> <snip>
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Error configuring: org.apache.maven.plugins:maven-install-
> plugin. Reason: ERROR: Cannot override read-only parameter:
> artifactId in goal: install:install-file
> </snip>
>
> From what I can tell this is using maven-install-plugin 2.1.
>
> Anyone know whats going on? I get the same problem with Maven
> 2.0.5 and 2.0.6 :-(
>
> --jason
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org