Last Version

Maven extension for building GlassFish 10.0-alpha-4

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.

Categories

Categories

GlassFish Container Application Servers Maven Build Tools
GroupId

GroupId

org.glassfish.build
ArtifactId

ArtifactId

maven-glassfish-extension
Version

Version

10.0-alpha-4
Type

Type

jar
Description

Description

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.

Download maven-glassfish-extension 10.0-alpha-4


<!-- https://jarcasting.com/artifacts/org.glassfish.build/maven-glassfish-extension/ -->
<dependency>
    <groupId>org.glassfish.build</groupId>
    <artifactId>maven-glassfish-extension</artifactId>
    <version>10.0-alpha-4</version>
</dependency>
// https://jarcasting.com/artifacts/org.glassfish.build/maven-glassfish-extension/
implementation 'org.glassfish.build:maven-glassfish-extension:10.0-alpha-4'
// https://jarcasting.com/artifacts/org.glassfish.build/maven-glassfish-extension/
implementation ("org.glassfish.build:maven-glassfish-extension:10.0-alpha-4")
'org.glassfish.build:maven-glassfish-extension:jar:10.0-alpha-4'
<dependency org="org.glassfish.build" name="maven-glassfish-extension" rev="10.0-alpha-4">
  <artifact name="maven-glassfish-extension" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.glassfish.build', module='maven-glassfish-extension', version='10.0-alpha-4')
)
libraryDependencies += "org.glassfish.build" % "maven-glassfish-extension" % "10.0-alpha-4"
[org.glassfish.build/maven-glassfish-extension "10.0-alpha-4"]

Dependencies

compile (1)

Group / Artifact Type Version
org.apache.maven : maven-core jar 2.0.7

Project Modules

There are no modules declared in this project.