[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_84475 ]
Aaron Digulla commented on MECLIPSE-134:
----------------------------------------
> you can already use the "outputDir" parameter
I tried that and it didn't work. Can you please post an example?
Also, in the code, you write:
212 /**
213 * The default output directory
214 *
215 * @parameter expression="${outputDirectory}" alias="outputDirectory"
default-value="${project.build.outputDirectory}"
216 * @required
217 */
218 private File buildOutputDirectory;
That means I have to define a property "outputDirectory" instead of
"buildOutputDirectory", right?
I'd suggest to use "eclipse.outputDirectory" instead because outputDirectory is
easily confused with the Maven config element.
> target/classes not acceptable for eclipse
> -----------------------------------------
>
> Key: MECLIPSE-134
> URL: http://jira.codehaus.org/browse/MECLIPSE-134
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.0, 2.1, 2.2
> Reporter: Jörg Hohwiller
> Assigned To: fabrizio giustina
> Priority: Minor
>
> "mvn eclipse:eclipse" causes an eclipse configuration where the classfiles
> generated by eclipse go to the same directory as the classes generated by
> maven. This is extremly evil! Eclipse and maven are independent tools and
> should therefore not compile to the same target folder causing side effects.
> Especially when "mvn clean" is called and you re-run an existing application
> inside eclipse, and get a NoClassDefFoundError you can get slightly confused.
> Please use anything else than "target/...". My suggestion would be
> ".eclipse-build".
--
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
