| 描述 |
GlassFish build depends on properly functioning several custom lifecycle mappings and
artifact handlers. Because these are necessary to resolve dependencies and to run
"gf:run" goal and etc., it is critical that these extensions be made available to
Maven early on during Maven execution.
This definition was originally in maven-glassfish-plugin, which was integrated
into Maven POM through <plugin>/<extensions>true marking, but after
a series of debugging to resolve artifact resolution failure problems, it turns
out that that doesn't cause Maven to load components early enough.
I tried to circumbent the prolem by also registering the maven-glassfish-plugin
as an extension module (via <build>/<extensions/<extension>), b |
