[ http://jira.codehaus.org/browse/MNG-1795?page=comments#action_53155 ]
mike perham commented on MNG-1795:
----------------------------------
This plugin configuration works for me. Is there some reason why you can't use
this?
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<outputDirectory>bin</outputDirectory>
</configuration>
</plugin>
> 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]
