[ http://jira.codehaus.org/browse/MCLEAN-19?page=comments#action_77192 ] 
            
Ian Springer commented on MCLEAN-19:
------------------------------------

Note, after some more thought, I think it makes sense for the 'outputDirectory' 
prop to remain read-only, to force all plugins to share the same output 
directory (i.e. project.build.outputDirectory). So I think the better way to 
support my use case is for Maven to allow profiles to override 
project.build.outputDirectory. I have filed another issue for this 
(http://jira.codehaus.org/browse/MNG-2598), so feel free to close this issue.

Thanks,
Ian


> 'outputDirectory' configuration property should not be read-only
> ----------------------------------------------------------------
>
>                 Key: MCLEAN-19
>                 URL: http://jira.codehaus.org/browse/MCLEAN-19
>             Project: Maven 2.x Clean Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Ian Springer
>
> 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 set the outputDirectory config prop in the maven-clean-plugin, 
> the maven-compiler-plugin, and the maven-resources-plugin. The 
> maven-resources-plugin allowed me to modify the outputDirectory without any 
> complaints, but the maven-clean-plugin and maven-compiler-plugin did not... 
> The clean plugin fails with the following error:
> [INFO] Error configuring: org.apache.maven.plugins:maven-clean-plugin. 
> Reason: ERROR: Cannot override read-only parameter: outputDirectory in goal: 
> clean:clean
> 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

        

Reply via email to