[
https://issues.apache.org/jira/browse/MCLEAN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958656#comment-17958656
]
Olivier Lamy commented on MCLEAN-19:
------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-clean-plugin#207|https://github.com/apache/maven-clean-plugin/issues/207].
> 'outputDirectory' configuration property should not be read-only
> ----------------------------------------------------------------
>
> Key: MCLEAN-19
> URL: https://issues.apache.org/jira/browse/MCLEAN-19
> Project: Maven Clean Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Ian P. Springer
> Assignee: Siveton Vincent
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
