Repository

Artifacts/Jars

Popular Tags

ajax analysis annotations ant apache api archetype aspect asynchronously beans binding bpm build buildsystem bytecode cache cms codecoverage codehaus collections concurrency container database directory distributed doc eclipse ejb esb format framework graph graphics hadoop hibernate html http ide imap io jbi jdbc jdo jini jms jmx jndi jsf jsp language logging mail maven metadata microsoft mock net osgi parser pdf persistence plugin pool portal portlet query regexp rmi rpc rss ruleengine scheduling scm scripting security server servlet soa soap socket spring ssh svg swt system taglib template testing transaction ui web webdav webframework webserver webservice workflow xml xquery xslt

[See All Tags]
home » org.glassfish.build

Group: org.glassfish.build



Artifact Last Version Popularity Description
maven-glassfishbuild-extension (124)
Maven extension for building GlassFish 		3.2.2 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 /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 /), 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.
parent-build-pom (2)
GlassFish Build Utilities 		3.2.2
maven-glassfishbuild-plugin (124)
GlassFish v3 Maven2 plugin 		3.2.2
maven-glassfish-extension (11)
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 /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 /), 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.
build (133)
GlassFish Build Utilities 		10.0-alpha-4
maven-glassfish-plugin (11)
GlassFish v3 Maven2 plugin 		10.0-alpha-4
legal (1)
Legal License for glassfish code 		1.0
glassfishbuild-maven-plugin (9)
GlassFishBuild Maven Plugin 		3.2.20
command-security-maven-plugin (5)
Command Security Plug-in 		1.0.4 Maven plug-in for checking that AdminCommand implementers address command authorization
spec-version-maven-plugin (3)
Spec Version Maven Plugin 		1.2