Ok I think I understand now. The project.build.plugins are searched so
that they would override the pluginGroup metadata for the prefix...AND
all the default plugins are now in project.build.plugins instead of
pluginManagement. This is the bigger change here but the upshot is
that effective-pom now
Brian Fox:
I put this on my desktop and ran:
c:\Users\brianf\Desktop>mvn help:effective-pom
And it started downloading all updated versions of the
plugins...plugins that aren't being used in this execution and aren't
referenced in the pom directly.
In short, the plugin JARs (and only those)
Last night I was looking at an irc user's pom for a parsing error:
4.0.0
org.lwjgl
lwjgl-linux-64
2.4.2
newdawnsoftware
http://www.newdawnsoftware.com/maven2
net.java.games
jinput
2.0.1
net.java.games
jinput
