[
https://jira.codehaus.org/browse/MCOMPILER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272350#comment-272350
]
Frédéric Camblor commented on MCOMPILER-156:
--------------------------------------------
Why wouldn't you provide #outputDirectory parameter to javac instead of
${project.build.outputDirectory} ?
maven-compiler-plugin wouldn't have rights on this ? (it would be managed by
maven core ?)
> Make outputDirectory & testOutputDirectory configurable at the plugin level
> ---------------------------------------------------------------------------
>
> Key: MCOMPILER-156
> URL: https://jira.codehaus.org/browse/MCOMPILER-156
> Project: Maven 2.x Compiler Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.2
> Reporter: Frédéric Camblor
> Priority: Trivial
> Attachments: MCOMPILER-156.patch
>
>
> I'd like to change the test output directory for a particular
> maven-compiler-plugin execution.
> Problem is : maven-compiler-plugin is relying on
> /project/build/outputDirectory|testOutputDirectory pom configuration for
> compilation.
> It would be nicer to have these parameters configurables (obviously with a
> default value to ${project.build.outputDirectory} or
> ${project.build.testOutputDirectory} to keep backward compatibility)
> My use case is for some "incubation tests" I'd want to compile but not to
> execute (because, as they are named, they are in failure (incubation) for the
> moment .. test first methodology :)).
> I would be able to define this design by executing maven-compiler-plugin on
> an additionnal execution while overriding the testOutputDirectory (because I
> don't want to execute these tests).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
