[
http://jira.codehaus.org/browse/MECLIPSE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151294#action_151294
]
Rustam Abdullaev commented on MECLIPSE-422:
-------------------------------------------
buildOutputDirectory is useless; I can't think of a scenario in which one would
want to mix test- and non-test folders, but it seems like the plugin was
designed that way, according to this comment in EclipsePlugin.java:
// If using the standard output location, don't mix the test output
into it.
A possible workaround:
Specify the output directory at the project level under /project/build, for
example, like this:
<outputDirectory>WebContent/WEB-INF/classes</outputDirectory>
And don't specify buildOutputDirectory - the eclipse plugin will automatically
use the default outputDirectory for non-test classes only.
Note For a web app, also specify it under
/project/build/plugins/plugin[artifactId="maven-war-plugin"]/configuration,
like this:
<warSourceDirectory>WebContent</warSourceDirectory>
> Cannot specify a separate output directory for test classes when custom
> buildOutputDirectory set
> ------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-422
> URL: http://jira.codehaus.org/browse/MECLIPSE-422
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> Affects Versions: 2.5
> Reporter: Mark Hobson
>
> As soon as buildOutputDirectory is set to a non-default value the output
> directories for all source folders are the same. It should be possible to
> specify a buildTestOutputDirectory to separate main and test classes, as is
> the default behaviour when buildOutputDirectory is not set.
--
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
