You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bob Tiernay (JIRA)" <ji...@codehaus.org> on 2010/10/25 14:19:05 UTC
[jira] Created: (MECLIPSE-672) Add Support for Adding
classpathentrys to .classpath
Add Support for Adding classpathentrys to .classpath
----------------------------------------------------
Key: MECLIPSE-672
URL: http://jira.codehaus.org/browse/MECLIPSE-672
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : Dependencies resolution and build path (.classpath)
Affects Versions: 2.8
Reporter: Bob Tiernay
One of the main issues with trying to configure a groovy / maven project within eclipse is that one must manually configure the classpath each time a project is materialized from SCM or created anew.
It would be extremely helpful if one could specify {{classpathentry}}s to be generated in {{.classpath}} so that when {{eclipse:eclipse}} or {{eclipse:m2eclipse}} is performed the following is produced:
{code:xml}
<classpathentry kind="src" output="target/classes" path="src/main/java" including="**/*.java"/>
<classpathentry kind="src" output="target/classes" path="src/main/groovy" including="**/*.groovy"/>
<classpathentry kind="src" output="target/test-classes" path="src/test/java" including="**/*.java"/>
<classpathentry kind="src" output="target/test-classes" path="src/test/groovy" including="**/*.groovy"/>
{code}
--
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