You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ian Springer (JIRA)" <ji...@codehaus.org> on 2006/10/10 19:33:53 UTC
[jira] Created: (MCOMPILER-44) 'outputDirectory' configuration
property should not be read-only
'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
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
[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration
property should not be read-only
Posted by "Ian Springer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77177 ]
Ian Springer commented on MCOMPILER-44:
---------------------------------------
Correction: The resources plugin allows the 'outputDirectory' prop to be modified, but the clean plugin does not.
I will file another JIRA in http://jira.codehaus.org/browse/MCLEAN to request that that plugin also remove the read-only restriction for 'outputDirectory' .
> '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
>
> 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
[jira] Closed: (MCOMPILER-44) 'outputDirectory' configuration
property should not be read-only
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration
property should not be read-only
Posted by "Ian Springer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77191 ]
Ian Springer commented on MCOMPILER-44:
---------------------------------------
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: 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
>
> 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
[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration
property should not be read-only
Posted by "Ian Springer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77179 ]
Ian Springer commented on MCOMPILER-44:
---------------------------------------
Note, I have filed a similar issue for the clean plugin - http://jira.codehaus.org/browse/MCLEAN-19.
> '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
>
> 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