Hey Max,
I think the problem here is with the pom.xml files. Prior to the m2e fix, there was no
way to store this information outside of the pom files. Obviously, they could have
created a dummy jar to make this work without the warning.
I'd actually start nuking this from the poms, which will force dev's to upgrade to
the latest m2e to get around this problem. Unfortunately, it looks like part of the
feature is "experimental."
Best,
Rob
----- Original Message -----
I'm not sure when it was introduced but it started to drive me
crazy..
We got this in our parent pom (and a few other plugins):
<!--This plugin's configuration is used to store Eclipse m2e
settings only.
It has no influence on the Maven build itself.-->
<!-- Workaround for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
Which seem to cause our build to spit out a warning for *every* damn
component:
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building gwt.all 1.1.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for
org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
X ~420.
Can we not avoid this ? didn't m2e actually get fixed to not require
these kind of changes....or at least have a way to dump this
[warning] on every build ? (i.e. shouldn't this not only be present
in a specific m2e profile ?!
Fred/Mickael, ?
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev