default Maven directory structure not used when generating .classpath file on
new project imported to Eclipse
-------------------------------------------------------------------------------------------------------------
Key: MECLIPSE-250
URL: http://jira.codehaus.org/browse/MECLIPSE-250
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Reporter: Tom Baker
The current m2eclipse plugin does not create .classpath files that honor the
standard Maven directory structure when it is used.
To reproduce this, start with a simple project that uses the default Maven
directory structure. Import the project into Eclipse as a regular project (not
as a Java, or a Maven project). At this point, the project does not have a
.classpath file.
Run 'Maven2 Enable'. The .classpath file that gets generated does not
correctly identify the default source folders and output folders based on the
standard Maven directory structure.
Here are sample contents of .classpath after running Maven2 Enable:
<classpathentry kind="src" path=""/>
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="bin"/>
Here is what I would have expected to see there:
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="src" path="src/test/java"/>
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con"
path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="target/classes"/>
I think that when generating this file, the plugin should dynamically determine
which of the standard directories contain source, and should add these entries
to the .classpath file.
--
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
