Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: M2Eclipse support
-
Labels:None
Description
Since eclipse has nice plugin http://m2eclipse.codehaus.org/ for maven2 projects, you should provide this type of project nature
below there are .project and .classpath files which has the declaration of m2 nature
przemek@przemek ~/mag/modules/web $ cat .project
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>mag-web</name>
<comment>Some project</comment>
<projects>
<project>mag-common</project>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.maven.ide.eclipse.maven2Builder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.maven.ide.eclipse.maven2Nature</nature>
</natures>
</projectDescription>
przemek@przemek ~/mag/modules/web $ cat .classpath
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="src" path="src/main/resources"/>
<classpathentry kind="src" path="src/main/webapp"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry exported="true" kind="src" path="/mag-common"/>
<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
<classpathentry kind="output" path="target/classes"/>
</classpath>
This feature would be very handy, because now in package explorer in eclipse there is a lot of dependencies shown in project, using m2 plugin they are all covered in library. Maybe you should provide some configuration option like
<configuration>
<useMavenPlugin>true</useMavenPlugin>
</configuration>
which would be false for default, so one no using this plugin won't feel the difference.
Issue Links
- duplicates
-
MECLIPSE-78
create eclipse projects which are m2eclipse ready
-
There is already an issue on this subject, http://jira.codehaus.org/browse/MECLIPSE-78.