[Stephen Cooper]

Quick update to anyone using “my” solution above:
I’ve given up on the m2eclipse plugin – it’s too unstable. I instead use mvn eclipse:eclipse and manually tweak the build path. It’s a bit of a bother having to help a large team navigate doing that, but it’s better than the stability issues of the m2eclipse plugin.

MyEclipse team – I think the m2eclipse plugin approach is the “correct” way to go about it, but it’s a plugin which is in serious need of some help.
a) on restart of eclipse, it will randomly fail to put any jar files in the “Maven dependencies” classpath library. The fastest way to get them back is to disable then re-enable the maven integration
b) in a nested project structure, where the parent pom changes, the changes aren’t picked up until you do a secrent incantation of ‘reindex local’ and disabling and re-enabling maven on every child project.

[Knut Erik Ballestad]

This message has not been recovered.

[James Carroll]

This message has not been recovered.

[Knut Erik Ballestad]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Aaron Digulla]

This message has not been recovered.

[lynnw]

This message has not been recovered.

[Stephen Cooper]

This message has not been recovered.

[msquared]

@digulla wrote:

Apart from that, the maven integration still won’t buy us much unless ME learns a way to say “deploy/do not deploy” on a per-file basis like IntelliJ does.

The maven scope and ME deployment issue is easily solved, see my post
https://www.genuitec.com/forums/topic/maven-integration/#post-270346

This thread is now FOUR (4) YEARS OLD but still MyEclipse doesn’t know a pom from a lollipop

The WTP project is a far better choice than MyEclipse for maven users:
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+WTP
Note that m2eclipse plugin already has an attribute now that MyEclipse could use with the following simple patch to com.genuitec.eclipse.ast.deploy.core.DeploymentUtil:

boolean deploy=true;
if (“org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER”.equals(iclasspathcontainer.getPath().toPortableString())){
for (int a=0; a<iclasspathentry1.getExtraAttributes().length; a++) {
IClasspathAttribute cpa = iclasspathentry1.getExtraAttributes()[a];
if (“org.eclipse.jst.component.nondependency”.equals(cpa.getName())) {
DeploymentCore.getDefault().log(“nondependency for ” + ipath2);
deploy = false;
break;
}
}
}
if (! deploy)
continue; // dont deploy this JAR

[Knut Erik Ballestad]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Knut Erik Ballestad]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[jacorob]

Little late, but just to keep the requests coming.. +6 from my team for Maven2 integration.

Bob
ERG

[Riyad Kalla]

Bob,
Never too late.

Can you be more specific about your team’s requirements for Maven? Just the dependnecy management? Build management? etc.

[Author]

Posts