[ http://jira.codehaus.org/browse/MNG-1795?page=comments#action_53157 ]
Matthew Beermann commented on MNG-1795: --------------------------------------- No, that's what I'll probably do in production, but if I understood http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html correctly, I should be able to do the same thing from the command line, too. Is this just an issue of the documentation being wrong? > eclipse:eclipse still setting .classpath's output to wrong directory > -------------------------------------------------------------------- > > Key: MNG-1795 > URL: http://jira.codehaus.org/browse/MNG-1795 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Versions: 2.0 > Reporter: Matthew Beermann > Fix For: 2.0.1 > > > When I run: > mvn -Dproject.build.outputDirectory=bin eclipse:eclipse > ...the resulting .classpath file still has: > <classpathentry kind="output" path="target/classes"/> > This looks like exactly what MNG-907 was meant to fix, and I think I have > that fix if I have version 2.0 of the plugin, but it's still busted obviously. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
