I updated the Maven Integration for Eclipse plugin to the one you pointed to (0.12.2.20110330-1446). I noticed that the Maven Integration for Eclipse WTP is still back at 0.11.1.20101108-1810.
I'm using Eclipse Helios on Mac OSX 10.6.7.
Here's what I found so far:
1) The dependency resolution works better, the 50+ transitive dependencies for the pom artifact (below) were correctly evaluated as "provided" as seen in the Dependency Hierarchy tab:
group id: org.jboss.jbossas
artifact id: jboss-as-client
However there was one dependency ant-launcher: 1.8.0  that didn't evaluate to any scope and so got deployed to the WEB-INF/lib of my war project when published to the app server. It's interesting to note that the ant-launcher dependency is the first leaf node of the first branch node in the dependency tree.
2) I have an ear file which contains a ejb 2.1 jar, an ejb 3.1 jar , a war and two standard jars. When running mvn package outside of eclipse the ear gets packaged correctly with 4 jars, a packaged war and a correctly generated application.xml. When using the Run As Maven Package command in eclipse the resultant ear file ends up with the ejb3.1 module and the war module being exploded.
On 07/04/2011, at 10:07 AM, Igor Fedorenko wrote:
For m2e 0.13, we plan to provide embedded maven runtime based on maven
3.0.3 as a separate item available from m2e marketplace. All external
dependencies are already locked for 3.7/Indigo release, so we won't be
able update "standard" m2e until after June.
We are also considering release m2e 0.12.2 to include maven 3.0.3 and
updated version of http transport layer. If you want to help us test
this new version, "warm-up" build is available from . We will
appreciate any feedback, positive and otherwise.
On 11-04-06 07:53 PM, Adam Lau wrote:
Is there a plan to move the embedded maven version from 3.0.2 to 3.0.3?
I'm currently being bitten by a bug in 3.0.2 to do with transitive
dependencies [http://jira.codehaus.org/browse/MNG-4982]. I think my only
work around is to put in explicit exclusions for 50+ transitive
dependencies. The problem manifests itself when m2eclipse/wtp is used to
deploy my war project to the app server (jboss). The war has a
dependency on my app server library pom jboss-as-client . The result is
that even though the jboss-as-client dependency is scoped as provided
some of the transitive dependencies get evaluated as scope compile and
get bundled in the WEB-INF/lib directory.
m2e-users mailing list
m2e-users mailing listm2e-users@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/m2e-users