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 shows all the default bindings to the user.
Previously it was all magic. That's a good tradeoff for a few
downloads the first time run.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to