[ http://jira.codehaus.org/browse/MCOMPILER-44?page=all ]
Carlos Sanchez closed MCOMPILER-44.
-----------------------------------
Assignee: Carlos Sanchez
Resolution: Won't Fix
> 'outputDirectory' configuration property should not be read-only
> ----------------------------------------------------------------
>
> Key: MCOMPILER-44
> URL: http://jira.codehaus.org/browse/MCOMPILER-44
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Ian Springer
> Assigned To: Carlos Sanchez
>
> I am trying to set up a 'dev' build profile that, when enabled, will cause my
> artifacts to be built directly to an exploded ejb-jar deployment dir, instead
> of target/classes/. The purpose is to make the development process more
> efficient by skipping a number of time-consuming intermediate mvn steps (i.e.
> jarring the artifact, copying the jar to the local repo, unjarring the
> artifact to its deploy/test location).
> Since profiles do not allow you to override project.build.outputDirectory, I
> proceeded to override the outputDirectory config props in the
> maven-clean-plugin, the maven-compiler-plugin, and the
> maven-resources-plugin. The maven-clean-plugin and the maven-resources-plugin
> allow me to modify the outputDirectory without any complaints, but the
> maven-compiler-plugin does not... It fails with the following error:
> [INFO] Error configuring: org.apache.maven.plugins:maven-compiler-plugin.
> Reason: ERROR: Cannot override read-only parameter: outputDirectory in goal:
> compiler:compile
> Please make this property non-read-only. Making it read-only seriously limits
> the flexibility of Maven2.
> Thanks,
> Ian
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
