Project Group: org.glassfish.build

Command Security Plug-in

org.glassfish.build : command-security-maven-plugin

Maven plug-in for checking that AdminCommand implementers address command authorization

Last Version: 1.0.14

Release Date:

GlassFishBuild Maven Plugin

org.glassfish.build : glassfishbuild-maven-plugin

Eclipse Enterprise for Java (EE4J) is an open source initiative to create standard APIs, implementations of those APIs, and technology compatibility kits for Java runtimes that enable development, deployment, and management of server-side and cloud-native applications.

Last Version: 3.2.28

Release Date:

GlassFish Maven Nexus Plugin

org.glassfish.build : gfnexus-maven-plugin

Java.net - The Source for Java Technology Collaboration

Last Version: 0.20

Release Date:

Maven extension for building GlassFish

org.glassfish.build : maven-glassfishbuild-extension

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>), but that apparently confuses Maven to no end --- I get build errors like this: [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin' This is obviously one of the problematic areas of Maven, so to avoid doing hack over hack, I'm simply moving the component definitions to its own module.

Last Version: 3.2.2

Release Date:

GlassFish Build Utilities

org.glassfish.build : parent-build-pom

Java.net - The Source for Java Technology Collaboration

Last Version: 3.2.2

Release Date:

GlassFish v3 Maven2 plugin

org.glassfish.build : maven-glassfishbuild-plugin

Java.net - The Source for Java Technology Collaboration

Last Version: 3.2.2

Release Date:

Maven extension for building GlassFish

org.glassfish.build : maven-glassfish-extension

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>), but that apparently confuses Maven to no end --- I get build errors like this: [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin 'org.apache.maven.plugins:maven-jar-plugin' This is obviously one of the problematic areas of Maven, so to avoid doing hack over hack, I'm simply moving the component definitions to its own module.

Last Version: 10.0-alpha-4

Release Date:

  • 1