[
http://jira.codehaus.org/browse/MECLIPSE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hannu Leinonen updated MECLIPSE-422:
------------------------------------
Attachment: fakeBuildOutputDirectory.patch
I also have an issue (and a patch) related to this. I included a
fakeBuildOutputDirectory variable to the plugin which means that it sets the
default output folder, but uses the specific output folders for the source
directories. This is essential for the Google Plugin for Eclipse development,
since it requires certain path for the default output directory. Otherwise I
can't run tests or use the Eclipse Java compiler. I'm hosting the patched
snapshot (with another patch of mine from
http://jira.codehaus.org/browse/MECLIPSE-402) in a Maven repository at
http://beardedgeeks.googlecode.com/svn/repository/snapshots/
> 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
> (.classpath)
> Affects Versions: 2.5
> Reporter: Mark Hobson
> Attachments: fakeBuildOutputDirectory.patch, separateOutputs.patch,
> testOutputDirectory.patch
>
>
> 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
