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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
