Re: [m2e-users] upgrade from m2eclipse 0.12.1 to 1.1.0

[Damien Tacheron <dtacheron@xxxxxxxx>]

This does not look like .classpath created by m2e 0.12. Are you sure
there is no MAVEN2_CLASSPATH_CONTAINER entry? Do you actually have
src/main/java/services configured as project java source directory in
pom.xml file?

-> you're right. I've made a mistake, this project use previous m2e plugin from sonatype, not from eclipse.org

Generally, you are expected to reimport your projects as existing maven
projects when migrating form m2e 0.12 to 1.x. I believe there is a
thirdparty extension to automate this, but I have not tried it personally.

-> i tried to import via "file / import / Existing Maven Project" but the result doesn't compile. It seems that the jar files referenced in the pom.xml are not visible for compiler

-> it got an error message. it guess that i have problem because i have multiple source directory  (all compliant with maven default layout)

Target JDK is derived from maven-compiler-plugin configuration of your
projects, which is 1.5 for maven 3.0.4 used by m2e. Eclipse is expected
to approximate 1.5 compile classpath using 1.6 libraries.

-> I'm not sure to understand. I didn't configure the maven compiler plugin in pom.xml. I suppose that i can ignore this point as it is internal to m2e ?

I will recreate new projects and "push" my source files inside. I think it will be much simpler.

Thanks 4 help

2012/7/9 Igor Fedorenko <igor@xxxxxxxxxxxxxx>

On 12-07-09 7:34 PM, Damien Tacheron wrote:

Hi,

I have just downloaded Eclipse Juno. And my previous projet which
compile normaly under Eclise Helios don't compile now.

Project compile normaly with command line. Dependency resolution seems
to not working under Eclipse Juno.

It seems that classpath file syntax have changed. i have commited these
files in the past and now i suppose that data are not recognized.

before :
..
<classpathentry kind="src" path="src/main/java/services"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
..

This does not look like .classpath created by m2e 0.12. Are you sure
there is no MAVEN2_CLASSPATH_CONTAINER entry? Do you actually have
src/main/java/services configured as project java source directory in
pom.xml file?

now (on a new project created with Juno) :
..
<classpathentry kind="src" output="target/classes" path="src/main/java">
<attributes>
<attribute name="optional" value="true"/>
<attribute name="maven.pomderived" value="true"/>
</attributes>
</classpathentry>

<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5">
<attributes>
<attribute name="maven.pomderived" value="true"/>
</attributes>
</classpathentry>
<classpathentry kind="con"
path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
<attributes>
<attribute name="maven.pomderived" value="true"/>
</attributes>
</classpathentry>

What is not correct exactly?

Does exists a migration guide or a guideline ?
Or, i have to re-create my projects ?  (mmm... not quite elegant)

Generally, you are expected to reimport your projects as existing maven
projects when migrating form m2e 0.12 to 1.x. I believe there is a
thirdparty extension to automate this, but I have not tried it personally.

And why do i have a reference to J2SE 1.5 ([..] StandardVMType/J2SE-1.5)
as my Eclipse Juno run with a 1.6 JDK (which is the only jdk knonw by
Eclipse)

Target JDK is derived from maven-compiler-plugin configuration of your
projects, which is 1.5 for maven 3.0.4 used by m2e. Eclipse is expected
to approximate 1.5 compile classpath using 1.6 libraries.

--
Regards,
Igor
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users