You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2007/05/26 16:47:58 UTC

[jira] Closed: (MCLEAN-19) 'outputDirectory' configuration property should not be read-only

     [ http://jira.codehaus.org/browse/MCLEAN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton closed MCLEAN-19.
---------------------------------

         Assignee: Vincent Siveton
       Resolution: Won't Fix
    Fix Version/s: 2.2

wont fix like MCOMPILER-44

> '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
>            Assignee: Vincent Siveton
>             Fix For: 2.2
>
>
> 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