/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." > mvncenter: org.glassfish.build:maven-glassfishbuild-extension
m

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 /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.
maven manager cause apache glassfish enough extensions plugin info handlers prolem after doesn avoid over errors hack component lifecycle depends custom these problems moving unable functioning definitions available like registering goal mojo properly that failure simply doing executing areas several load components this early series plugins made tried resolution through build turns execution because critical problematic during dependencies mappings marking apparently debugging internal find circumbent module resolve definition error obviously into true extension integrated artifact which originally confuses necessary also
Aggregated version Version Update time
3.2 3.2.2 Sep 14, 2011
3.2.1 Jul 22, 2011
3.2-b06 May 11, 2011
3.2-b05 May 04, 2011
3.2-b04 Apr 27, 2011
3.2-b03 Apr 20, 2011
3.2-b02 Apr 13, 2011
3.2-b01 Apr 07, 2011
3.1 3.1.1 Jul 29, 2011
3.1.1-b11 Jul 12, 2011
3.1.1-b10 Jul 03, 2011
3.1.1-b09 Jun 24, 2011
3.1.1-b08 Jun 17, 2011
3.1.1-b07 Jun 16, 2011
3.1.1-b06 May 29, 2011
3.1.1-b05 May 17, 2011
3.1.1-b04 May 05, 2011
3.1.1-b03 Apr 30, 2011
3.1.1-b02 Apr 22, 2011
3.1.1-b01 Apr 14, 2011
3.1 Feb 28, 2011
3.1-b41 Feb 06, 2011
3.1-b40 Feb 05, 2011
3.1-b39 Jan 28, 2011
3.1-b38 Jan 19, 2011
3.1-b37 Jan 12, 2011
3.1-b36 Jan 05, 2011
3.1-b35 Dec 29, 2010
3.1-b34 Dec 23, 2010
3.1-b33 Dec 16, 2010
3.1-b32 Dec 08, 2010
3.1-b31 Dec 01, 2010
3.1-b30 Nov 18, 2010
3.1-b28 Nov 10, 2010
3.1-b27 Nov 04, 2010
3.1-b26 Oct 29, 2010
3.1-b25 Oct 20, 2010
3.1-b24 Oct 13, 2010
3.1-b23 Oct 06, 2010
3.1-b22 Sep 29, 2010
124 Records