| Hi Rafael,
Thanks for your quick reply. Unfortunately the plugin always uses the embedded version for dependency resolution. I have set the installation to point to 3.0.3 which fixed my issue when I use Run As maven commands but it didn't fix the wtp deploy scenario.
regards,
Adam. On 07/04/2011, at 10:08 AM, Rafael Vanderlei wrote: Adam, if you want m2eclipse to work with Maven 3.0.3 (or any other version than the one embedded) you can install it on your machine and then go in Window > Preferences > Maven > Installations and change to use it instead of embedded version.
Regards, Rafael. On Wed, Apr 6, 2011 at 8:53 PM, Adam Lau <adam@xxxxxxxxxx> 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@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
|
