jar

org.glassfish.build : maven-glassfishbuild-extension

Maven & Gradle

Sep 14, 2011

Maven extension for building GlassFish · 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.

Table Of Contents

Latest Version

Download org.glassfish.build : maven-glassfishbuild-extension JAR file - Latest Versions:

All Versions

Download org.glassfish.build : maven-glassfishbuild-extension JAR file - All Versions:

Version Vulnerabilities Size Updated
3.2.x
3.2
3.1.x
3.1
3.0.x
3.0

View Java Class Source Code in JAR file

  1. Download JD-GUI to open JAR file and explore Java source code file (.class .java)
  2. Click menu "File → Open File..." or just drag-and-drop the JAR file in the JD-GUI window maven-glassfishbuild-extension-3.2.2.jar file.
    Once you open a JAR file, all the java classes in the JAR file will be displayed.