[GLASSFISH-19314] Update jar license: phase 1 Created: 10/Nov/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b60
Fix Version/s: 4.1

Type: Bug Priority: Critical
Reporter: Joe Di Pol Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 15 minutes
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-19315 Update jar license: phase 2 Open

 Description   

See phase 1 described here:

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Copyrights+and+Licenses+for+Jar+Files






[GLASSFISH-19425] Nucleus build Created: 10/Dec/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b74
Fix Version/s: 4.1

Type: Improvement Priority: Critical
Reporter: Nazrul Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We will need to setup Nucleus and GlassFish build such that...
1) We need to be able to branch nucleus source to address concurrent development of multiple releases
2) We need to have a system for versioning nucleus that is both sane and accommodates the limitations of maven versioning
3) We need to re-work the automated builds so that they are flexible and can accommodate building multiple nucleus based distributions

Romain has a proposal for this and working on the issue. So, assigning to him.



 Comments   
Comment by Joe Di Pol [ 05/Mar/13 ]

We likely won't change the GF4 build over to the nucleus pipeline until after Java EE 7 RI/SDK ship, so re-targeting this to 4.0.1





[GLASSFISH-19610] occasional build failure in nucleus/core/context-propagation module Created: 31/Jan/13  Updated: 08/Mar/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b70
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Tom Mueller Assignee: sfjeandrolet
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X 10.8.2, Java SE 7 Update 11, Java SE 7 Update 9



 Description   

Occasionally when building nucleus, the build fails in the nucleus/core/context-propagation module with the following message:

[INFO] — maven-surefire-plugin:2.4.3:test (default-test) @ context-propagation —
[INFO] Surefire report directory: /Users/tomuell/ws/cloudlogic/main/nucleus/core/context-propagation/target/surefire-reports
java.lang.RuntimeException: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
at mockit.internal.startup.JDK6AgentLoader.attachToThisVM(JDK6AgentLoader.java:91)
at mockit.internal.startup.JDK6AgentLoader.loadAgent(JDK6AgentLoader.java:57)
at mockit.internal.startup.AgentInitialization.initializeAccordingToJDKVersion(AgentInitialization.java:21)
at mockit.internal.startup.Startup.initializeIfNeeded(Startup.java:96)
at mockit.internal.startup.Startup.initializeIfPossible(Startup.java:111)
at org.junit.runner.Runner.<clinit>(Runner.java:22)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.booter.SurefireBooter.getTestSets(SurefireBooter.java:455)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkPerTestSet(SurefireBooter.java:406)
at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:249)
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:537)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
at sun.tools.attach.BsdVirtualMachine.<init>(BsdVirtualMachine.java:90)
at sun.tools.attach.BsdAttachProvider.attachVirtualMachine(BsdAttachProvider.java:63)
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:178)
at mockit.internal.startup.JDK6AgentLoader.attachToThisVM(JDK6AgentLoader.java:88)
... 47 more
[INFO] ------------------------------

and at the end:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test (default-test) on project context-propagation: org.junit.runner.Runner; nested exception is java.lang.NoClassDefFoundError: org.junit.runner.Runner -> [Help 1]

This has been reported by several people, so I'm opening an issue on this.

If the build is restarted, it completes. I've never seen this happen two times in a row. Typically, if this happens, it happens on the first build of the day, right after doing an "svn up". However, I don't know that the "svn up" has anything to do with the failure.

I don't know yet how to reproduce this problem on demand.



 Comments   
Comment by Tim Quinn [ 02/Feb/13 ]

For what it's worth, I have just seen this for the first time.

Mac OS X 10.7, Java 1.7.0_09. The build failed immediately after an svn update; the next build was fine.

Comment by marina vatkina [ 02/Feb/13 ]

I'm seeing it for quite some time. I think it started after I switched to JDK7 (or may be upgraded to OS X 10.8.2, which happened almost at the same time).

Comment by Pavel Bucek [ 04/Feb/13 ]

same here

Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /usr/share/maven
Java version: 1.7.0_13, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_13.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"

[INFO] Test Source directory: /Users/pavel/glassfish/trunk/main/nucleus/core/context-propagation/target/generated-sources/hk2-config-generator/src/test/java added.
[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ context-propagation ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.4:testCompile (default-testCompile) @ context-propagation ---
[INFO] Compiling 51 source files to /Users/pavel/glassfish/trunk/main/nucleus/core/context-propagation/target/test-classes
[INFO] 
[INFO] --- hk2-inhabitant-generator:2.1.55:generateInhabitants (test) @ context-propagation ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ context-propagation ---
[INFO] Surefire report directory: /Users/pavel/glassfish/trunk/main/nucleus/core/context-propagation/target/surefire-reports
java.lang.RuntimeException: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
	at mockit.internal.startup.JDK6AgentLoader.attachToThisVM(JDK6AgentLoader.java:91)
	at mockit.internal.startup.JDK6AgentLoader.loadAgent(JDK6AgentLoader.java:57)
	at mockit.internal.startup.AgentInitialization.initializeAccordingToJDKVersion(AgentInitialization.java:21)
	at mockit.internal.startup.Startup.initializeIfNeeded(Startup.java:96)
	at mockit.internal.startup.Startup.initializeIfPossible(Startup.java:111)
	at org.junit.runner.Runner.<clinit>(Runner.java:22)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
	at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
	at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
	at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
	at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
	at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
	at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
	at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.apache.maven.surefire.booter.SurefireBooter.getTestSets(SurefireBooter.java:455)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkPerTestSet(SurefireBooter.java:406)
	at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:249)
	at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:537)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
	at sun.tools.attach.BsdVirtualMachine.<init>(BsdVirtualMachine.java:90)
	at sun.tools.attach.BsdAttachProvider.attachVirtualMachine(BsdAttachProvider.java:63)
	at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:178)
	at mockit.internal.startup.JDK6AgentLoader.attachToThisVM(JDK6AgentLoader.java:88)
	... 47 more
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] GlassFish Nucleus Parent Project .................. SUCCESS [26.753s]
[INFO] Distribution Fragments for various OSGi platforms . SUCCESS [0.019s]
[INFO] Apache Felix, associated bundles and conf files ... SUCCESS [1.297s]
[INFO] Scattered Archive APIs of Glassfish ............... SUCCESS [1.685s]
[INFO] GlassFish Nucleus Grizzly modules ................. SUCCESS [0.065s]
[INFO] Nucleus Grizzly jars Combining .................... SUCCESS [3.617s]
[INFO] Public APIs of Glassfish V3 ....................... SUCCESS [10.299s]
[INFO] Repackaged nucleus external modules ............... SUCCESS [0.027s]
[INFO] j-interop repackaged as a module .................. SUCCESS [1.464s]
[INFO] GlassFish Nucleus Common modules .................. SUCCESS [0.021s]
[INFO] Common Utilities .................................. SUCCESS [8.138s]
[INFO] Simple Public APIs of Glassfish V3 ................ SUCCESS [0.275s]
[INFO] GlassFish Nucleus Core modules .................... SUCCESS [0.022s]
[INFO] Appserver Core Bootstraping Classes ............... SUCCESS [1.047s]
[INFO] GlassFish Tests related modules ................... SUCCESS [0.031s]
[INFO] Test utilities .................................... SUCCESS [0.282s]
[INFO] Admin Modules ..................................... SUCCESS [0.019s]
[INFO] admin-config-api .................................. SUCCESS [9.148s]
[INFO] Private APIs of Glassfish V3 ...................... SUCCESS [1.466s]
[INFO] Nucleus Security Parent ........................... SUCCESS [0.021s]
[INFO] GlassFish SSL Implementation Module ............... SUCCESS [0.572s]
[INFO] GlassFish Nucleus Deployment Related Modules ...... SUCCESS [0.021s]
[INFO] Deployment Related Common Classes ................. SUCCESS [1.865s]
[INFO] ldapbp repackaged as a module ..................... SUCCESS [0.270s]
[INFO] Security Core Classes ............................. SUCCESS [2.492s]
[INFO] Security Services and SPI ......................... SUCCESS [10.757s]
[INFO] admin-util ........................................ SUCCESS [8.066s]
[INFO] Admin CLI bridge command to the OSGi Shell ........ SUCCESS [0.556s]
[INFO] OSGi Container .................................... SUCCESS [0.398s]
[INFO] Cluster ........................................... SUCCESS [0.018s]
[INFO] cluster-common .................................... SUCCESS [0.816s]
[INFO] flashlight-framework .............................. SUCCESS [1.239s]
[INFO] trilead-ssh2 repackaged as a module ............... SUCCESS [0.541s]
[INFO] Cluster SSH Provisioning .......................... SUCCESS [0.582s]
[INFO] Appserver Logging Classes ......................... SUCCESS [1.546s]
[INFO] GlassFish API Exporter Module ..................... SUCCESS [0.174s]
[INFO] Kernel Classes .................................... SUCCESS [3.532s]
[INFO] GMS Bootstrap Module .............................. SUCCESS [0.291s]
[INFO] cluster-admin ..................................... SUCCESS [0.992s]
[INFO] admin-launcher .................................... SUCCESS [0.852s]
[INFO] admin-cli ......................................... SUCCESS [1.194s]
[INFO] admin-server-management ........................... SUCCESS [4.420s]
[INFO] cluster-cli ....................................... SUCCESS [2.027s]
[INFO] GMS Module ........................................ SUCCESS [0.875s]
[INFO] GMS Bootstrap Module l10n ......................... SUCCESS [0.147s]
[INFO] cluster-cli l10n .................................. SUCCESS [0.181s]
[INFO] Cluster SSH Provisioning l10n ..................... SUCCESS [0.217s]
[INFO] cluster-common l10n ............................... SUCCESS [0.134s]
[INFO] cluster-admin l10n ................................ SUCCESS [0.231s]
[INFO] jmxremote_optional repackaged as a module ......... SUCCESS [1.078s]
[INFO] Glassfish MBeanServer support ..................... SUCCESS [0.693s]
[INFO] AMX V3 Core ....................................... SUCCESS [4.202s]
[INFO] Common Utilities l10n ............................. SUCCESS [0.324s]
[INFO] Private APIs of Glassfish l10n .................... SUCCESS [0.155s]
[INFO] Public APIs of Glassfish l10n ..................... SUCCESS [0.134s]
[INFO] GlassFish Extra JRE Packages ...................... SUCCESS [0.104s]
[INFO] Glassfish logging classes l10n .................... SUCCESS [0.109s]
[INFO] Kernel classes l10n ............................... SUCCESS [0.250s]
[INFO] Context Propagation ............................... FAILURE [6.411s]
[INFO] admin-monitoring .................................. SKIPPED
[INFO] GlassFish Admin REST Parent ....................... SKIPPED
[INFO] GlassFish Admin REST Client ....................... SKIPPED
[INFO] Connector for GlassFish Admin REST Service ........ SKIPPED
[INFO] GlassFish Admin REST Service ...................... SKIPPED
[INFO] GlassFish Admin REST Service l10n ................. SKIPPED
[INFO] admin-launcher l10n ............................... SKIPPED
[INFO] admin-monitoring l10n ............................. SKIPPED
[INFO] admin-config-api l10n ............................. SKIPPED
[INFO] admin-cli l10n .................................... SKIPPED
[INFO] admin-server-management l10n ...................... SKIPPED
[INFO] admin-util l10n ................................... SKIPPED
[INFO] Nucleus template .................................. SKIPPED
[INFO] flashlight-agent .................................. SKIPPED
[INFO] GlassFish Flashlight Extra JDK Pkgs ............... SKIPPED
[INFO] Flashlight ........................................ SKIPPED
[INFO] flashlight-framework l10n ......................... SKIPPED
[INFO] Deployment Related Admin Classes .................. SKIPPED
[INFO] AutoDeploy Classes ................................ SKIPPED
[INFO] Set of DTDs for Nucleus distributions ............. SKIPPED
[INFO] Set of schemas for Nucleus ........................ SKIPPED
[INFO] Deployment Related Common Classes l10n ............ SKIPPED
[INFO] AutoDeploy Related Admin Classes l10n ............. SKIPPED
[INFO] AutoDeploy Classes l10n ........................... SKIPPED
[INFO] virtualbox client SDK repackaged as module ........ SKIPPED
[INFO] antlr.all version 2.7.6 repackaged as a module .... SKIPPED
[INFO] Glassfish Nucleus packages ........................ SKIPPED
[INFO] Felix Nucleus Package ............................. SKIPPED
[INFO] Nucleus HK2 Package ............................... SKIPPED
[INFO] Nucleus Grizzly Package ........................... SKIPPED
[INFO] Nucleus Jersey Package ............................ SKIPPED
[INFO] Nucleus Package ................................... SKIPPED
[INFO] Nucleus Base CORBA APIs Package ................... SKIPPED
[INFO] Nucleus Commons Package ........................... SKIPPED
[INFO] Nucleus Shoal Package ............................. SKIPPED
[INFO] Nucleus Clustering Package ........................ SKIPPED
[INFO] Nucleus Management Package ........................ SKIPPED
[INFO] Glassfish OSGi Support Package .................... SKIPPED
[INFO] Glassfish JMX Package ............................. SKIPPED
[INFO] Nucleus Clustering l10n Package ................... SKIPPED
[INFO] Security Core Classes l10n ........................ SKIPPED
[INFO] Nucleus Commons Package l10n package .............. SKIPPED
[INFO] Nucleus l10n Package .............................. SKIPPED
[INFO] Nucleus Management l10n Package ................... SKIPPED
[INFO] Nucleus distributions ............................. SKIPPED
[INFO] Glassfish Atomic Distribution ..................... SKIPPED
[INFO] Nucleus Distribution .............................. SKIPPED
[INFO] nucleus.tests.utils-ng ............................ SKIPPED
[INFO] Diagnostics ....................................... SKIPPED
[INFO] Diagnostics API ................................... SKIPPED
[INFO] GlassFish Diagnostics Context ..................... SKIPPED
[INFO] nucleus.resources ................................. SKIPPED
[INFO] GlassFish Appserver Parent Project ................ SKIPPED
[INFO] Super POM for Java EE API modules ................. SKIPPED
[INFO] javax.jws API v.1.1 ............................... SKIPPED
[INFO] javax.xml.soap API v.1.3 .......................... SKIPPED
[INFO] JavaEE APi ........................................ SKIPPED
[INFO] GlassFish Common modules .......................... SKIPPED
[INFO] stats77 ........................................... SKIPPED
[INFO] javax.management.j2ee API v.1.1 ................... SKIPPED
[INFO] GlassFish Java EE Annotation Framework ............ SKIPPED
[INFO] GlassFish Deployment Related Modules .............. SKIPPED
[INFO] Deployment Object Library ......................... SKIPPED
[INFO] AXM JavaEE ........................................ SKIPPED
[INFO] javax.security.auth.message API v.1.0 ............. SKIPPED
[INFO] javax.security.jacc API v.1.4 ..................... SKIPPED
[INFO] GlassFish Security Parent ......................... SKIPPED
[INFO] Jaspic Provider Framework ......................... SKIPPED
[INFO] GlassFish Transaction modules ..................... SKIPPED
[INFO] Transaction Service Internal API .................. SKIPPED
[INFO] GlassFish Resources infrastructure related modules  SKIPPED
[INFO] Resources Connector ............................... SKIPPED
[INFO] Connectors Parent ................................. SKIPPED
[INFO] Connectors Private APIs for GlassFish Containers .. SKIPPED
[INFO] GlassFish EJB container related modules ........... SKIPPED
[INFO] EJB container Internal API ........................ SKIPPED
[INFO] Repackaged external modules ....................... SKIPPED
[INFO] libpam4j repackaged as a module ................... SKIPPED
[INFO] Java EE Security Core Classes ..................... SKIPPED
[INFO] Java EE Management JSR 77 MEJB .................... SKIPPED
[INFO] mejb distribution fragment ........................ SKIPPED
[INFO] Java EE dependent public APIs of Glassfish V3 ..... SKIPPED
[INFO] Glassfish Naming .................................. SKIPPED
[INFO] Container Common .................................. SKIPPED
[INFO] GlassFish Java EE Annotation Framework l10n ....... SKIPPED
[INFO] Container Common l10n ............................. SKIPPED
[INFO] glassfish-naming l10n ............................. SKIPPED
[INFO] stats77 l10n ...................................... SKIPPED
[INFO] GlassFish HA modules .............................. SKIPPED
[INFO] GlassFish ha-file-store ........................... SKIPPED
[INFO] GlassFish ha-shoal-cache-bootstrap ................ SKIPPED
[INFO] GlassFish ha-shoal-store .......................... SKIPPED
[INFO] Set of DTDs for GlassFish Java EE distributions ... SKIPPED
[INFO] Set of schemas for Java EE ........................ SKIPPED
[INFO] Deployment Client Classes and Interfaces .......... SKIPPED
[INFO] Deployment Related JavaEE Core Classes ............ SKIPPED
[INFO] GlassFish Web container related modules ........... SKIPPED
[INFO] Connector for GlassFish Web Container ............. SKIPPED
[INFO] EJB Container connector for Glassfish ............. SKIPPED
[INFO] GlassFish Connectors Connector .................... SKIPPED
[INFO] App Client Modules ................................ SKIPPED
[INFO] GlassFish App Client Server-side Modules .......... SKIPPED
[INFO] GlassFish AppClient Server-Side Connector ......... SKIPPED
[INFO] Deployment Related JavaEE Full Profile Classes .... SKIPPED
[INFO] JSR-88 JAR and dist. fragment ..................... SKIPPED
[INFO] JSR-88 implementation declaration JAR ............. SKIPPED
[INFO] JSR-88 dist. fragment ............................. SKIPPED
[INFO] Deployment Related JavaEE Core Classes l10n ....... SKIPPED
[INFO] Deployment Object Library ......................... SKIPPED
[INFO] Deployment JavaEE Full l10n ....................... SKIPPED
[INFO] Deployment Client Classes and Interfaces l10n ..... SKIPPED
[INFO] Admin Modules ..................................... SKIPPED
[INFO] Backup Restore classes ............................ SKIPPED
[INFO] App Server CLI Skinning Class ..................... SKIPPED
[INFO] admin-cli-optional ................................ SKIPPED
[INFO] admin-core ........................................ SKIPPED
[INFO] Backup Restore classes l10n ....................... SKIPPED
[INFO] admin-cli-optional-l10n ........................... SKIPPED
[INFO] Appserver template ................................ SKIPPED
[INFO] GlassFish Core modules ............................ SKIPPED
[INFO] Java EE related distributions kernel Classes ...... SKIPPED
[INFO] GlassFish API Exporter Module Fragment ............ SKIPPED
[INFO] JTA Implementation for Glassfish .................. SKIPPED
[INFO] GlassFish ORB related modules ..................... SKIPPED
[INFO] GlassFish ORB connector implementation ............ SKIPPED
[INFO] JavaMail Resources Support related modules ........ SKIPPED
[INFO] JavaMail Connector ................................ SKIPPED
[INFO] Connectors Runtime ................................ SKIPPED
[INFO] JTS Implementation for Glassfish .................. SKIPPED
[INFO] JTS Implementation for Glassfish l10n ............. SKIPPED
[INFO] JTA Implementation for Glassfish l10n ............. SKIPPED
[INFO] Transaction Service Internal API l10n ............. SKIPPED
[INFO] Web Container Naming Utilities .................... SKIPPED
[INFO] Web Container Common Utilities .................... SKIPPED
[INFO] Core Servlet Container ............................ SKIPPED
[INFO] JSTL implementation connector module .............. SKIPPED
[INFO] Web module command line interface ................. SKIPPED
[INFO] Web container and GUI plug-in common classes ...... SKIPPED
[INFO] WebTier Security Integration ...................... SKIPPED
[INFO] GlassFish Web container embedded related modules .. SKIPPED
[INFO] GlassFish Web container Embedded APIs ............. SKIPPED
[INFO] Server-Sent Events ................................ SKIPPED
[INFO] Web Container glue code ........................... SKIPPED
[INFO] JSF implementation connector module ............... SKIPPED
[INFO] JSP caching taglib connector module ............... SKIPPED
[INFO] Web Container HA code ............................. SKIPPED
[INFO] Web Related Implementations for GlassFish ......... SKIPPED
[INFO] Weld connector for glassfish ...................... SKIPPED
[INFO] Weld integration for glassfish .................... SKIPPED
[INFO] Weld Integration Fragment ......................... SKIPPED
[INFO] Fragment bundle for Weld related testing .......... SKIPPED
[INFO] Web container and GUI plug-in common classes l10n . SKIPPED
[INFO] Web module command line interface l10n ............ SKIPPED
[INFO] Core Servlet Container l10n ....................... SKIPPED
[INFO] Web Container glue code l10n ...................... SKIPPED
[INFO] GlassFish persistence related modules ............. SKIPPED
[INFO] Common persistence code between JPA and CMP ....... SKIPPED
[INFO] GlassFish Core EJB container implementation ....... SKIPPED
[INFO] Full EJB Container add-ons ........................ SKIPPED
[INFO] EJB Timer Service Application ..................... SKIPPED
[INFO] GlassFish EJB timer app database init scripts ..... SKIPPED
[INFO] EJB tier for GlassFish ............................ SKIPPED
[INFO] EJB Container connector for Glassfish l10n ........ SKIPPED
[INFO] GlassFish Core EJB container implementation l10n .. SKIPPED
[INFO] GlassFish resources runtime ....................... SKIPPED
[INFO] GlassFish JavaMail runtime ........................ SKIPPED
[INFO] JavaMail Connector l10n ........................... SKIPPED
[INFO] Resiyrces Connector l10n .......................... SKIPPED
[INFO] JavaEE Connector Architecture Descriptors ......... SKIPPED
[INFO] Connectors Inbound Support ........................ SKIPPED
[INFO] Work Management ................................... SKIPPED
[INFO] JDBC Module ....................................... SKIPPED
[INFO] JDBC Config Module ................................ SKIPPED
[INFO] Connectors admin .................................. SKIPPED
[INFO] Connectors Internal APi l10n ...................... SKIPPED
[INFO] Connectors Runtime l10n ........................... SKIPPED
[INFO] Work Management l10n .............................. SKIPPED
[INFO] Connectors admin l10n ............................. SKIPPED
[INFO] Connectors Inbound Support l10n ................... SKIPPED
[INFO] GlassFish Load-Balancer Plugin related modules .... SKIPPED
[INFO] Load Balancer Internal API ........................ SKIPPED
[INFO] Load-Balancer admin ............................... SKIPPED
[INFO] Load-Balancer admin l10n .......................... SKIPPED
[INFO] Load Balancer Internal API l10n ................... SKIPPED
[INFO] GlassFish JMS modules ............................. SKIPPED
[INFO] JMS Connector Module for Runtime .................. SKIPPED
[INFO] JMS Module ........................................ SKIPPED
[INFO] JMS admin ......................................... SKIPPED
[INFO] JMS Injection Module for Runtime .................. SKIPPED
[INFO] JMS module l10n ................................... SKIPPED
[INFO] JMS admin l10n .................................... SKIPPED
[INFO] JMS Connector Module for Runtime l10n ............. SKIPPED
[INFO] JMS Injection Module for Runtime l10n ............. SKIPPED
[INFO] JDBC Resource Adapter ............................. SKIPPED
[INFO] Core JDBC Resource Adapter classes ................ SKIPPED
[INFO] JDBC 30 related classes for JDBC Resource Adapter . SKIPPED
[INFO] JDBC 40 related classes for JDBC Resource Adapter . SKIPPED
[INFO] JDBC Templates .................................... SKIPPED
[INFO] Distribution Module for JDBC Resource Adapter ..... SKIPPED
[INFO] Core JDBC Resource Adapter classes l10n ........... SKIPPED
[INFO] JDBC Runtime Module ............................... SKIPPED
[INFO] JDBC admin ........................................ SKIPPED
[INFO] JDBC admin l10n ................................... SKIPPED
[INFO] JDBC Config Module l10n ........................... SKIPPED
[INFO] JDBC Runtime Module l10n .......................... SKIPPED
[INFO] GlassFish Oracle JDBC Packages .................... SKIPPED
[INFO] Connector for JPA runtime in glassfish ............ SKIPPED
[INFO] JPA container for glassfish ....................... SKIPPED
[INFO] Declaring EclipseLink dependencies ................ SKIPPED
[INFO] GlassFish cmp related modules ..................... SKIPPED
[INFO] utility module for cmp ............................ SKIPPED
[INFO] model module for cmp .............................. SKIPPED
[INFO] Database Generator module for cmp ................. SKIPPED
[INFO] ejb-mapping module for cmp ........................ SKIPPED
[INFO] enhancer module for cmp ........................... SKIPPED
[INFO] internal-api module for cmp ....................... SKIPPED
[INFO] Entity Bean container ............................. SKIPPED
[INFO] support-sqlstore module for cmp ................... SKIPPED
[INFO] support ejb module for cmp ........................ SKIPPED
[INFO] GlassFish cmp scripts ............................. SKIPPED
[INFO] CMP tier for GlassFish ............................ SKIPPED
[INFO] JPA container for glassfish l10n .................. SKIPPED
[INFO] GlassFish cmp related modules l10n ................ SKIPPED
[INFO] Database Generator module for cmp l10n ............ SKIPPED
[INFO] utility module for cmp l10n ....................... SKIPPED
[INFO] support ejb module for cmp l10n ................... SKIPPED
[INFO] ejb-mapping module for cmp l10n ................... SKIPPED
[INFO] support-sqlstore module for cmp l10n .............. SKIPPED
[INFO] enhancer module for cmp l10n ...................... SKIPPED
[INFO] model module for cmp l10n ......................... SKIPPED
[INFO] Concurrency Utilities Modules ..................... SKIPPED
[INFO] Concurrent Config Module .......................... SKIPPED
[INFO] Concurrent Admin Module ........................... SKIPPED
[INFO] Batch runtime connector for Glassfish ............. SKIPPED
[INFO] GlassFish Extras modules .......................... SKIPPED
[INFO] GlassFish JavaEE Manifest pom ..................... SKIPPED
[INFO] GlassFish javaee.jar .............................. SKIPPED
[INFO] GlassFish javaee.jar distribution fragment ........ SKIPPED
[INFO] GlassFish appserv-rt Manifest pom ................. SKIPPED
[INFO] GlassFish appserv-rt.jar .......................... SKIPPED
[INFO] GlassFish appserv-rt distribution fragment ........ SKIPPED
[INFO] DataProvider ...................................... SKIPPED
[INFO] Admin Console Integration ......................... SKIPPED
[INFO] Admin Console Integration ......................... SKIPPED
[INFO] Admin Console Packages ............................ SKIPPED
[INFO] Admin Console Common .............................. SKIPPED
[INFO] Registration ...................................... SKIPPED
[INFO] Registration API .................................. SKIPPED
[INFO] Registration Impl ................................. SKIPPED
[INFO] GlassFish Registration ............................ SKIPPED
[INFO] Admin Console Core Jar ............................ SKIPPED
[INFO] Admin Console Clustering Support Plugin ........... SKIPPED
[INFO] Admin Console Community Edition Theme Plugin ...... SKIPPED
[INFO] Admin Console Web Container Plugin ................ SKIPPED
[INFO] Admin Console JTS Plugin .......................... SKIPPED
[INFO] Admin Console JDBC Plugin ......................... SKIPPED
[INFO] Admin Console Connectors Plugin ................... SKIPPED
[INFO] Admin Console JMS Plugin .......................... SKIPPED
[INFO] Admin Console EJB Container Plugin ................ SKIPPED
[INFO] Admin Console EJB Local (Lite) Plugin ............. SKIPPED
[INFO] Admin Console Corba Plugin ........................ SKIPPED
[INFO] Admin Console Full distribution plugin ............ SKIPPED
[INFO] Admin Console Update Center Plugin ................ SKIPPED
[INFO] Admin Console WAR ................................. SKIPPED
[INFO] Admin Console Install Fragment for Web distro ..... SKIPPED
[INFO] Admin Console Update Center Plugin l10n ........... SKIPPED
[INFO] Admin Console Full distribution plugin l10n ....... SKIPPED
[INFO] Admin Console Common l10n ......................... SKIPPED
[INFO] Admin Console Corba Plugin l10n ................... SKIPPED
[INFO] Admin Console JTS Plugin l10n ..................... SKIPPED
[INFO] Admin Console Community Edition Theme Plugin l10n . SKIPPED
[INFO] Admin Console Web Container Plugin l10n ........... SKIPPED
[INFO] Admin Console JMS Plugin l10n ..................... SKIPPED
[INFO] Admin Console JDBC Plugin l10n .................... SKIPPED
[INFO] Admin Console EJB Container Plugin l10n ........... SKIPPED
[INFO] Admin Console Clustering Support Plugin l10n ...... SKIPPED
[INFO] Admin Console Connectors Plugin l10n .............. SKIPPED
[INFO] Admin Console EJB Local (Lite) Plugin l10n ........ SKIPPED
[INFO] Admin Console Core Jar l10n ....................... SKIPPED
[INFO] Embedded GlassFish Shell .......................... SKIPPED
[INFO] Embedded GlassFish Shell dist. fragment ........... SKIPPED
[INFO] Glassfish packages ................................ SKIPPED
[INFO] Glassfish CMP Package ............................. SKIPPED
[INFO] Glassfish Commons Package ......................... SKIPPED
[INFO] Glassfish Clustering Package ...................... SKIPPED
[INFO] JAXR GlassFish System RA Assembly ................. SKIPPED
[INFO] Ant repackaging ................................... SKIPPED
[INFO] Glassfish Commons for Full Distribution ........... SKIPPED
[INFO] Corba Package ..................................... SKIPPED
[INFO] Base CORBA APIs Package ........................... SKIPPED
[INFO] GlassFish ORB interface layer implementation ...... SKIPPED
[INFO] Ejb Security Integration .......................... SKIPPED
[INFO] GlassFish ORB enabler implementation .............. SKIPPED
[INFO] Glassfish EJB Package ............................. SKIPPED
[INFO] Glassfish EJB Lite Container Package .............. SKIPPED
[INFO] GlassFish HK2 Package ............................. SKIPPED
[INFO] Glassfish Grizzly Package ......................... SKIPPED
[INFO] Grizzly Glassfish Extra modules ................... SKIPPED
[INFO] GlassFish Grizzly adapter container implementation  SKIPPED
[INFO] Glassfish Grizzly extra jars Combining ............ SKIPPED
[INFO] Glassfish Grizzly Package ......................... SKIPPED
[INFO] Glassfish Connector Package ....................... SKIPPED
[INFO] Glassfish JCDI Package ............................ SKIPPED
[INFO] Glassfish JDBC Package ............................ SKIPPED
[INFO] JMS GlassFish System RA Assembly .................. SKIPPED
[INFO] Glassfish Java Message Service .................... SKIPPED
[INFO] Glassfish JPA Package ............................. SKIPPED
[INFO] Glassfish JSF Package ............................. SKIPPED
[INFO] Glassfish Transaction Package ..................... SKIPPED
[INFO] Glassfish Java Transaction Service ................ SKIPPED
[INFO] Glassfish Management Package ...................... SKIPPED
[INFO] Glassfish Nucleus Package ......................... SKIPPED
[INFO] Glassfish Web Container Package ................... SKIPPED
[INFO] Jersey Package .................................... SKIPPED
[INFO] GlassFish Web Services related modules ............ SKIPPED
[INFO] JSR-109 implementation to deploy Metro ............ SKIPPED
[INFO] GlassFish Metro Glue Code ......................... SKIPPED
[INFO] Connector for GlassFish Web Services Container .... SKIPPED
[INFO] SOAP/TCP integration code ......................... SKIPPED
[INFO] WebServices Security and JSR 196 implementation ... SKIPPED
[INFO] GlassFish webservices scripts ..................... SKIPPED
[INFO] GlassFish Metro Related Fragments ................. SKIPPED
[INFO] Metro Package ..................................... SKIPPED
[INFO] Embedded GlassFish Static Shell ................... SKIPPED
[INFO] Embedded GlassFish Static Shell dist. fragment .... SKIPPED
[INFO] Embedded GlassFish Shell Jars ..................... SKIPPED
[INFO] JavaDB to be bundled into GlassFish ............... SKIPPED
[INFO] Glassfish Legal content distribution fragment ..... SKIPPED
[INFO] Appserver Base Bundle ............................. SKIPPED
[INFO] Felix Package ..................................... SKIPPED
[INFO] Shoal Package ..................................... SKIPPED
[INFO] Glassfish JavaHelp Package ........................ SKIPPED
[INFO] Glassfish Registration Package .................... SKIPPED
[INFO] Glassfish HA Package .............................. SKIPPED
[INFO] Glassfish Admin GUI Package ....................... SKIPPED
[INFO] Verifier implementation module .................... SKIPPED
[INFO] GlassFish Verifier Extension Bundle ............... SKIPPED
[INFO] Verifier scripts .................................. SKIPPED
[INFO] Verifier Package .................................. SKIPPED
[INFO] App Client - client-side modules .................. SKIPPED
[INFO] ACC Config Classes (JAXB) ......................... SKIPPED
[INFO] Appclient Security Integration .................... SKIPPED
[INFO] Client OSGi module (including ACC) ................ SKIPPED
[INFO] Client library (including ACC) .................... SKIPPED
[INFO] GlassFish appclient scripts ....................... SKIPPED
[INFO] GlassFish AppClient Server-Side Core .............. SKIPPED
[INFO] Glassfish Application Client Package .............. SKIPPED
[INFO] Java DB Package ................................... SKIPPED
[INFO] MQ Package ........................................ SKIPPED
[INFO] A Pluggable InMemory JACC Provider ................ SKIPPED
[INFO] Glassfish Commons for Web Profile Distribution .... SKIPPED
[INFO] Glassfish OSGi Support Package .................... SKIPPED
[INFO] Glassfish OSGi HTTP Service package ............... SKIPPED
[INFO] Console extensions for OSGi platforms ............. SKIPPED
[INFO] Felix Web Console Extension for GlassFish ......... SKIPPED
[INFO] GlassFish OSGi Console Plugin ..................... SKIPPED
[INFO] Glassfish OSGi Management console package ......... SKIPPED
[INFO] Glassfish Web Profile Incorporation Package ....... SKIPPED
[INFO] Glassfish Full Profile Incorporation Package ...... SKIPPED
[INFO] Glassfish Web Profile Metapackage ................. SKIPPED
[INFO] Glassfish Full Profile Metapackage ................ SKIPPED
[INFO] Glassfish OSGi Feature Pack Incorporation Package . SKIPPED
[INFO] Glassfish OSGi Feature Pack Metapackage ........... SKIPPED
[INFO] Ant tasks ......................................... SKIPPED
[INFO] GlassFish Ant Tasks Package ....................... SKIPPED
[INFO] GlassFish AppClient Server-Side Core l10n ......... SKIPPED
[INFO] Client OSGi module (including ACC) Localization ... SKIPPED
[INFO] Client library (including ACC) Localization ....... SKIPPED
[INFO] Glassfish Application Client l10n Package ......... SKIPPED
[INFO] Glassfish cluster l10n Package .................... SKIPPED
[INFO] Glassfish CMP l10n Package ........................ SKIPPED
[INFO] Glassfish Commons for Full Distribution l10n ...... SKIPPED
[INFO] Glassfish Commons l10n Package .................... SKIPPED
[INFO] Glassfish EJB l10n Package ........................ SKIPPED
[INFO] Glassfish EJB Lite Container l10n Package ......... SKIPPED
[INFO] Glassfish Admin GUI Localization Package .......... SKIPPED
[INFO] Glassfish Connector l10n Package .................. SKIPPED
[INFO] Glassfish JDBC l10n Package ....................... SKIPPED
[INFO] Glassfish Java Message Service l10n ............... SKIPPED
[INFO] Glassfish JPA l10n Package ........................ SKIPPED
[INFO] Glassfish Transaction Package l10n ................ SKIPPED
[INFO] Glassfish Java Transaction Service l10n ........... SKIPPED
[INFO] Glassfish Nucleus l10n Package .................... SKIPPED
[INFO] Verifier implementation module l10n ............... SKIPPED
[INFO] Glassfish verifier l10n Package ................... SKIPPED
[INFO] Glassfish Web Container l10n Package .............. SKIPPED
[INFO] JSR-109 implementation to deploy Metro l10n ....... SKIPPED
[INFO] WebServices Security and JSR 196 l10n ............. SKIPPED
[INFO] Metro l10n Package ................................ SKIPPED
[INFO] Glassfish Management Package l10n Package ......... SKIPPED
[INFO] Java EE Security Core Classes l10n ................ SKIPPED
[INFO] GlassFish ORB connector implementation l10n ....... SKIPPED
[INFO] Glassfish Commons Web l10n Package ................ SKIPPED
[INFO] OSGi Console Plugin for Admin Console l10n ........ SKIPPED
[INFO] Glassfish OSGi Management console l10n Package .... SKIPPED
[INFO] Registration Impl l10n ............................ SKIPPED
[INFO] Glassfish Registration l10n Package ............... SKIPPED
[INFO] Glassfish JMX Package ............................. SKIPPED
[INFO] Glassfish EntityBeans Container Package ........... SKIPPED
[INFO] JSON Package ...................................... SKIPPED
[INFO] Service tag registry file distribution fragment ... SKIPPED
[INFO] Glassfish distributions ........................... SKIPPED
[INFO] Glassfish Minnow Distribution ..................... SKIPPED
[INFO] Glassfish Web Distribution ........................ SKIPPED
[INFO] Glassfish Distribution ............................ SKIPPED
[INFO] Security Related Implementatios for GlassFish ..... SKIPPED
[INFO] Security DOL Integration l10n ..................... SKIPPED
[INFO] GlassFish Tests related modules ................... SKIPPED
[INFO] btrace jar files .................................. SKIPPED
[INFO] GlassFish Flashlight Client ....................... SKIPPED
[INFO] Flashlight ........................................ SKIPPED
[INFO] GlassFish Main Parent Project ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:08.266s
[INFO] Finished at: Mon Feb 04 13:49:30 CET 2013
[INFO] Final Memory: 236M/738M
[INFO] ------------------------------------------------------------------------
Comment by Anissa Lam [ 13/Feb/13 ]

I have never seen this before except today when i was trying out different setup to solve a Netbeans' problem.
What i found out is:

  • if i just check out main, ie, without the existence of it's parent pom.xml (all/pom.xml), the build failed at context-propagation. Everytime.

then it will always succeed. I have never encounter this issue in this setup.

Comment by sfjeandrolet [ 15/Feb/13 ]

I am not sure if the other participants are seeing the same issue as Anissa. In the case where they see the following stack trace,

java.lang.RuntimeException: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded
at mockit.internal.startup.JDK6AgentLoader.attachToThisVM(JDK6AgentLoader.java:91)
at mockit.internal.startup.JDK6AgentLoader.loadAgent(JDK6AgentLoader.java:57)
at mockit.internal.startup.AgentInitialization.initializeAccordingToJDKVersion(AgentInitialization.java:21)
at mockit.internal.startup.Startup.initializeIfNeeded(Startup.java:96)
at mockit.internal.startup.Startup.initializeIfPossible(Startup.java:111)
at org.junit.runner.Runner.<clinit>(Runner.java:22)
This code path should not be used by jmockit. I believe it is executing it because the agent was not connected as per the directive in the effective pom.

<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4.3</version>
<executions>
<execution>
<id>default-test</id>
<phase>test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<argLine>-javaagent:"$

{settings.localRepository}"/com/googlecode/jmockit/jmockit/0.999.15/jmockit-0.999.15.jar</argLine>
<forkMode>always</forkMode>
<useSystemClassLoader>true</useSystemClassLoader>
</configuration>
</execution>
</executions>
<configuration>
<argLine>-javaagent:"${settings.localRepository}

"/com/googlecode/jmockit/jmockit/0.999.15/jmockit-0.999.15.jar</argLine>
<forkMode>always</forkMode>
<useSystemClassLoader>true</useSystemClassLoader>
</configuration>
</plugin>

Is it possible that maven it not always consistent in computing the effective pom?

Participants,
Before you run the build in a situation where you expect it to fail, can you check that effective pom contains the above pluggin configuration? If for some reason maven does not always compute the effective pom the same way, then this becomes a maven bug. Please update the bug report with your findings.

Comment by Tom Mueller [ 15/Feb/13 ]

If I run:

mvn help:effective-pom -Doutput=effective-pom.xml

at the top level (which is where I run the build that fails), it doesn't include the details for the context-propagation module. So do you main to run help:effective-pom on the context-propagation module? i.e.:

mvn -f nucleus/core/context-propagation/pom.xml help:effective-pom -Doutput=effective-pom.xml

Comment by marina vatkina [ 01/Mar/13 ]

It's not that svn affects it, it's the local maven repo update. I've removed part of my local repo trying to build 3.1.2, and the build failed.

Comment by Tom Mueller [ 08/Mar/13 ]

Even with the most recent change to the POM file in context-propagation, I still got the failure today. Maybe this is because the jmockit dependency is still listed, so surefire is apparently still trying to use jmockit to run the tests.





[GLASSFISH-20746] support building GlassFish with maven 3.1.x Created: 07/Aug/13  Updated: 07/Aug/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Romain Grécourt Assignee: trilokagarwal
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: build, maven, maven-plugin

 Description   

Maven 3.1.0 breaks plugin compatibility.

It introduces usage of @Inject annotation and enforces aether (official lib for resolving dependency / artifacts).

All official plugins and most of the codehaus plugins have been updated.
We will have to upgrade all of the ones used in our workspace.

Then all in-house plugins (e.g hk2 plugins, glassfishbuild plugin and so on) will have to drop usage of javadoc / plexus specific annotation and move to the new model.






[GLASSFISH-64] Make all man pages available on all platforms Created: 27/Oct/05  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: cm151579 Assignee: vr127953
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 64

 Description   

Need to make all man pages viewable through the man command on all platforms.
Currently, they are all available only on Solaris, because Solaris can take
SGML-formatted man pages. NB, the asadmin man page content IS available
everywhere through the asadmin help command--but man pages for other commands
(~15) are not available at all ex-Solaris.

The binary build could make them available on Linux and Windows (w/Cygwin or
MKS) by using the Solaris catman command to convert the SGML pages to nroff
format, and then include the nroff files in the binary. The SGML man pages are
in CVS at /appserv-docs/sman/man1 and /man8.



 Comments   
Comment by cm151579 [ 28/Oct/05 ]

Adding Carla to cc list.

Comment by cm151579 [ 31/Jul/06 ]

Reassigning to Hanan, who is taking over as AS doc lead.

Comment by hl34125 [ 09/Aug/06 ]

Vipin,
This is an RFE for the next appserver release. We currently have only the
asadmin mpages available on all platforms and need to have all the utilities'
mpages available.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.





[GLASSFISH-1095] Installer gives no indication that it has done anything Created: 05/Sep/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: timboudreau Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,095

 Description   

The Glassfish installer provides no user feedback after the license is agreed to

  • you're left waiting for something to happen, not knowing that it has already
    happened.

This violates the basics of responsive UIs - there needs to be at least some
visual feedback that it is done, and ideally it should give some idea what it
has done.



 Comments   
Comment by dpatil [ 05/Sep/06 ]

Once you accept the issue, it should print the unjar log messages of the jar
file. Which OS you are running this? Pls update your env details like JAVA_HOME etc.

Normally it should print the log messages of unjarring the glassfish jar file
after you accept the license..

Comment by timboudreau [ 05/Sep/06 ]

It does print to the command line; however, that's not exactly normal installer
behavior; the Swing UI should show progress and let the user know that it has
been installed (some UI to select a location would be nice as well).

Generally a Swing app writing output to the console is not going to be noticed
by the user.

(BTW, when I tried to just use Mozilla's Open item in its download manager, I
got a message from the VM that the main class could not be found, though this
worked fine from the command line...but my copy of Mozilla has the JDK 1.3
plugin installed, so it may be invoking that vm [don't ask why I have 1.3...]).

Thanks for the quick response!

Comment by dpatil [ 06/Sep/06 ]

In GlassFish, we use a simple installer generator that can show a license
click-through before installation.
https://poormans-installer.dev.java.net/
There is a plan for another installer which may be more user-friendly.

Comment by timboudreau [ 06/Sep/06 ]

I'm thinking I should make a simple installer a demo app for my wizard project -
http://wizard.dev.java.net - Solaris is already using it for their installer. A
simple example would probably need almost no reworking for you to use it, and a
generator utility would be easy.

Comment by dpatil [ 06/Sep/06 ]

Sounds great! You are welcome to provide the demo app! will add this to the
GlassFish installer if it serves the purpose..

Comment by dpatil [ 12/Mar/07 ]

downgrading to P4, as its really a RFE

Comment by timboudreau [ 12/Mar/07 ]

Sorry, software not giving feedback to the user that it has done something the
user requested (esp. something as far-reaching as installing software!) is a
usability/responsiveness bug.

Apropos of that:
http://www.useit.com/papers/responsetime.html
http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html

Comment by dpatil [ 26/Mar/07 ]

This is really a RFE to change GlassFish Installer using GUI. Product already
has GUI based installer but cannot be published yet, so we don't have plan to
write another GUI based installer for GlassFish V2 looking at the timeframe.
So to set the expectation right, this issue won't be fixed for GlassFish V2 or
9.1 FCS.

Comment by gfbugbridge [ 05/Apr/07 ]

<BT6543245>

Comment by sridatta [ 10/Apr/07 ]

changing to enhancement based on previous comment.

Comment by timboudreau [ 10/Apr/07 ]

Well, I stand by my earlier comment. A usability bug is a bug, period. Make it
an enhancement if you want - I just worry that a lot of development teams turn
things into "enhancements" as a way of not fixing them.

So will this issue be addressed in the next version?

Comment by sridatta [ 13/Apr/07 ]

This will not be fixed for v2 due to resource/time constraints. There a real
installer in the distribution delivered on java.sun.com/javaee. It should make
you happy. Let us know if it does not.

Also, if you are willing to fix it, we will be happy to take it

thanks
-Sridatta

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1675] JAR file installer naming issue Created: 06/Dec/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: jzacker Assignee: dpatil
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,675

 Description   

thw download page for glassfish downloads the JAR files for all operating
systems under the same name. It would be helpful if the JAR for for Linux had
the word 'linux' in it, and the same goes for Windows/Solaris.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 18/Aug/08 ]

Moving to appropriate subcategory.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3330] Move Boilerplate out of the way Created: 12/Jul/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Byron Nevins Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: All


Issuezilla Id: 3,330

 Description   

Every source file has 35 lines of license legalese at the top of the file. Thus
developers and users have to first scroll scroll past this stuff for every
single file again and again and again.

Why not put this verbose comment at the BOTTOM of every file – the next time
the message changes?



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3500] Module with no NB project Created: 12/Aug/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Byron Nevins Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: All


Issuezilla Id: 3,500

 Description   

There is no NetBeans project for the appserv-commons-ee module

It would be nice if it was added.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-11422] See if empty src/main/resources/META-INF/MANIFEST.MF are needed in various javax modules Created: 11/Jan/10  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Sanjeeb Sahoo Assignee: janey
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,422
Tags: 3_1-exclude

 Description   

Empty MANIFEST.MF have been checked into various javax modules in v3. See if
there is a better way to handle this.



 Comments   
Comment by Sanjeeb Sahoo [ 11/Jan/10 ]

assigning to myself

Comment by Sanjeeb Sahoo [ 21/Jan/10 ]

Since it is going to take time to get rid of the empty MANIFEST.MF files because
of the ways various plugins are configured, I have added a README file in source
tree explaining their existence:
Adding admin/javax.management.j2ee/src/main/resources/META-INF/README
Adding connectors/javax.resource/src/main/resources/META-INF/README
Adding deployment/javax.enterprise.deploy/src/main/resources/META-INF/README
Adding ejb/javax.ejb/src/main/resources/META-INF/README
Sending javaee-api/api-pom/pom.xml
Sending javaee-api/javax.javaee/pom.xml
Adding javaee-api/javax.javaee/src/main/resources/META-INF/README
Adding
security/javax.security.auth.message/src/main/resources/META-INF/README
Adding security/javax.security.jacc/src/main/resources/META-INF/README
Adding transaction/javax.transaction/src/main/resources/META-INF/README
Sending web/javax.servlet/pom.xml
Adding web/javax.servlet/src/main/resources/META-INF/README
Transmitting file data ............
Committed revision 35416.

Comment by janey [ 07/Oct/10 ]

Sahoo mentioned in the README that we may be able to avoid it now but I need to understand what is the
side effects of removing the empty MANIFEST.MF.

At this time, keeping the empty MANIFEST.MF does not impact the final 3.1 bundle, I propose to exclude
this in 3.1 release.

Adding keyword: 3.1-exclude.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by janey [ 07/Mar/12 ]

We should really cleanup the workspace and get rid of the empty MANIFEST files.
They are:

rw-rr- 1 jsyoung staff 0 Feb 23 20:00 ./main/appserver/connectors/javax.resource/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:57 ./main/appserver/deployment/dtds/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:57 ./main/appserver/deployment/javax.enterprise.deploy/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:57 ./main/appserver/deployment/schemas/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:59 ./main/appserver/ejb/javax.ejb/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:58 ./main/appserver/javaee-api/javax.javaee/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:59 ./main/appserver/security/javax.security.auth.message/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:59 ./main/appserver/security/javax.security.jacc/src/main/resources/META-INF/MANIFEST.MF
rw-rr- 1 jsyoung staff 0 Feb 23 19:58 ./main/appserver/transaction/javax.transaction/src/main/resources/META-INF/MANIFEST.MF





[GLASSFISH-19315] Update jar license: phase 2 Created: 10/Nov/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b60
Fix Version/s: 4.1

Type: Bug Priority: Major
Reporter: Joe Di Pol Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-19314 Update jar license: phase 1 Open

 Description   

See phase 2 described here:

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Copyrights+and+Licenses+for+Jar+Files

This can be tackled after Java EE 7 RI/SDK






[GLASSFISH-19771] publish javaee-schemas into maven for binary integration in GlassFish Created: 05/Mar/13  Updated: 05/Mar/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b78
Fix Version/s: future release

Type: New Feature Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: maven, schemas

 Description   

JavaEE schemas are built here: https://svn.java.net/svn/glassfish~svn/trunk/schemas/javaee7
Spec leads contribute individually.

Currently Hong build scrubs for changes then build and copy updated schemas into GlassFish svn repository.

We would need to agree on the maven coordinates (groupId/artifactId/version) to choose.
Instead of creating a bug zip file, I would prefer to publish each file separately, as a pre-staged zip file or directly as .xsd files

Since this is an ant build, we may convert it to maven (or wrap it to not disrupt anything) in order to version things correctly for maven releases.

Eventually we would split the dtds/schemas into invidual modules instead of most of them under the deployment module.






[GLASSFISH-19812] Prevent usage of proprietary API" warnings issued by java compiler during maven build, using compiler option Created: 08/Mar/13  Updated: 05/Mar/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b79
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Romain Grécourt Assignee: Joe Di Pol
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-20980 Convert private JDK API usage to new ... Resolved
depends on GLASSFISH-19798 usage of internal proprietary API in ... Open
depends on GLASSFISH-19799 usage of internal proprietary API in... Open
depends on GLASSFISH-19801 usage of internal proprietary API in... Open
depends on GLASSFISH-19802 usage of internal proprietary API in... Open
depends on GLASSFISH-19803 usage of internal proprietary API in... Open
depends on GLASSFISH-19804 usage of internal proprietary API in... Open
depends on GLASSFISH-19805 usage of internal proprietary API in... Open
depends on GLASSFISH-19806 usage of internal proprietary API in... Open
depends on GLASSFISH-19809 usage of internal proprietary API in... Open
depends on GLASSFISH-19811 usage of internal proprietary API in... Open
depends on GLASSFISH-19808 usage of internal proprietary API in... Resolved
depends on GLASSFISH-19810 usage of internal proprietary API in... Resolved
Related
is related to GLASSFISH-2888 Try to use standard JDK classes only Resolved
Tags: build, maven, proprietary-api, warning

 Description   

Get rid of all the warning "is internal proprietary API and may be removed in a future release" echoed by the java compiler during the maven build.

Then we can enforce a compiler flag to prevent the introduction of any new warning.



 Comments   
Comment by Romain Grécourt [ 08/Mar/13 ]

linking separate issues

Comment by Tim Quinn [ 13/Feb/14 ]

Adding link to another issue for a private API usage





[GLASSFISH-20431] Need glassfish-all javadocs Created: 29/Apr/13  Updated: 24/Jun/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b86_RC2
Fix Version/s: 4.0_b88_RC4

Type: Bug Priority: Major
Reporter: Joe Di Pol Assignee: Romain Grécourt
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

For GlassFish 3 we have:

https://glassfish.java.net/docs/v3/api/

we need a version of that for GlassFish 4 (https://glassfish.java.net/docs/4/api/)

The build currently generates only the Java EE 7 API javadocs.



 Comments   
Comment by Joe Di Pol [ 24/Jun/13 ]

Mike says published link should be: http://glassfish.java.net/docs/4/api/





[GLASSFISH-20833] Makes l10n jars, attached artifacts and not separate Maven artifact Created: 30/Sep/13  Updated: 30/Sep/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 week
Time Spent: Not Specified
Original Estimate: 1 week

Tags: l0n, maven

 Description   

Instead of having "dummy" poms to generate the l10n jars, those could be created as attached artifact and their workspace (i.e. src/main/resources) merged into their corresponding bundles.
This could allow more "maven automation" for creating l10n distribution based on the dependency graph.

Some other benefits: remove the number of modules in the reactor, remove the fake "sources.jar" and "javadoc.jar" that are created to satisfy the maven central requirement.






[GLASSFISH-20835] hook org.netbeans.external:ddl to glassfish's repackaged Netbeans artifacts Created: 01/Oct/13  Updated: 01/Oct/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days

Tags: finsbugs, maven, netbeans

 Description   

When running findbugs on the GlassFish workspace, findbugs issues the following messages:

[INFO] ------------------------------------------------------------------------
[INFO] Building ejb-mapping module for cmp 4.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- findbugs-maven-plugin:2.5.2:findbugs (default-cli) @ cmp-ejb-mapping ---
     [java] The following classes needed for analysis were missing:
     [java]   org.netbeans.lib.ddl.impl.DriverSpecification
     [java] Missing classes: 1

The missing class can be found in org.netbeans.exterrnal:ddl, however those artifacts are not in Maven central but in Netbeans repository http://bits.netbeans.org/maven2/.
Since this is only related to findbugs and an extra repository may affect the build, the correct workaround would be as follow:

    <!--
        Findbugs needs org.netbeans.external:ddl,
        we isolate it in a profile as it requires a separate repository definition.
    -->
    <profiles>
        <profile>
            <id>findbugs</id>
            <repositories>
                <repository>
                    <id>netbeans</id>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                    <url>http://bits.netbeans.org/maven2</url>
                </repository>
            </repositories>
            <dependencies>
                <dependency>
                    <groupId>org.netbeans.external</groupId>
                    <artifactId>ddl</artifactId>
                    <version>RELEASE65</version>
                </dependency>
            </dependencies>
        </profile>
    </profiles>

This may be due to our repackaged version of the NetBeans artifacts that may not reflect the dependencies correctly.
The proper way would be to republish the corresponding repackaged artifacts to add the dependency.

org.netbeans.external.ddl should be repackaged and published to maven central to avoid the extra repository definition.






[GLASSFISH-20838] Move 3rd party repackaged OSGi bundles out of the GlassFish workspace / build Created: 01/Oct/13  Updated: 15/Oct/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days

Tags: 3rdparty, maven, osgi, packaging

 Description   

The non OSGied 3rd party artifacts are repackaged in the packager/external modules (main/nucleus/packager/external and main/appserver/packager/external).

Those 3party artifacts don't change often, but are part of the GlassFish build and hence published as part of every published build of GlassFish.
Also, there is no easy way to figure out what version of the 3rd party is used as the GlassFish version is used.

Instead, we should release those modules separately.

This would allow us to binary integrate those repackaged osgi bundles in the build, removing a bunch of modules from the build and the confusion around the version.
I'd suggest we put them in https://svn.java.net/svn/glassfish~svn/trunk/external/modules/, and provide a release.sh script for each module (see https://svn.java.net/svn/glassfish~svn/trunk/api/javaee-api/javax.annotation/release.sh) to facilitate the release process.

Also, we could provide a standard wiki page that describes how to setup the "maven release" environment.

Here is a list of the involved modules:

  • antlr
  • j-interop
  • jmxremote_optional
  • ldapbp
  • trilead-ssh2
  • vboxjws
  • ant
  • dbschema
  • javadb
  • jaxr_ra
  • jmsra
  • libpam4j
  • schema2beans

Some of the repackaged artifacts are not issued from Maven workspace, hence their dependency graph maybe incorrect (or inexistant).
We can leverage that to remove some workarounds present in the GlassFish workspace:

  • findbugs needs org.netbeans.external:ddl when introspecting code that uses either dbschema or schema2beans
  • antlr maven plugin expect the original antlr dependency in the graph, however it's not provided by our repackaged artifact, hence we have to add the original antlr dependency just to satisfy the plugin. (see ./appserver/persistence/cmp/support-sqlstore/pom.xml)





[GLASSFISH-20855] move and mavenize major developer tests from glassfish v2 repository to trunk/appserver/tests Created: 15/Oct/13  Updated: 15/Apr/14

Status: Open
Project: glassfish
Component/s: build_system, test
Affects Version/s: 4.0
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 2 weeks
Time Spent: Not Specified
Original Estimate: 2 weeks
Environment:

any


Tags: devtest, glassfish, maven, test

 Description   
  • Current developer test suite are documented here: https://wikis.oracle.com/display/glassfish/DeveloperTestDashboard
  • Those test suites are owned by particular developer, they are responsible for monitoring the test results.
  • They can take some time to run, hence they are not required for every checkin but depending on the changes (owner will likely request it)

The codeline comes from GlassFish 2.x, the test codebase is still located in the v2 svn repository: https://svn.java.net/svn/glassfish~v2/trunk/appserv-tests/devtests/

Those tests suite are still developed, and are used to test the current GlassFish codeline.

  • They are using the infrastructure that is provided by the old workspace
  • It is based on ant and is sometime platform dependent (i.e, can't work on windows).
  • It requires shell environment configuration to run (PATH and environment variables used by the tests)

This improvement is about mavenizing some of those devtests with as few changes as possible, in order to provide the following:

  • No change in the source code
  • Only maven / jdk required, everything else is downloaded and configured on the fly via maven
  • A pom.xml wrapping the tests scenario (e.g. with profiles)
  • Test workspace nested under appserver/tests, in order to be tagged be each release

Some things nice to have:

  • Windows / UNIX profiles to help sorting the suite that supports windows or not.
  • Generation of standard junit/testng report for easier CI
  • Test coverage infra (with cobertura)

Here are the in-scope test suites:

  • deployment
  • ejb
  • security
  • admin
  • webtier

Eventually, some documentation should be written under appserver/tests to guide developers.






[GLASSFISH-21270] Source build is missing some jaxws-ri (+ policy) modules Created: 11/Dec/14  Updated: 11/Dec/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Joe Di Pol Assignee: trilokagarwal
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

An EE7 RI build error occurred when building metro-2.3.1-b419 which tries to
get and compile com.sun.xml.ws:policy:jar:sources:2.4. It seems
com.sun.xml.ws:policy:jar:sources:2.4 was not provided in Maven
repository yet.

We will address this by redeploying com.sun.xml.ws:policy:jar:sources:2.4 to maven central, but the long term fix is to add this to the RI source bundle.






[GLASSFISH-21319] javax.inject.jar missing in javaee.jar Created: 27/Feb/15  Updated: 27/Feb/15

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.1
Fix Version/s: future release

Type: Bug Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the GlassFish lib directory there's a javaee.jar that just contains
a manifest Class-Path header referring to other jar files. It's missing
javax.inject.jar. And it includes weld-osgi-bundle.jar, which has no javax
classes in it.






[GLASSFISH-21320] Automate check-up of Class-Path jar 'javaee.jar' Created: 27/Feb/15  Updated: 27/Feb/15

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.1
Fix Version/s: future release

Type: Task Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Verify that all the required javax.* classes are present in the Class-Path jar 'javaee.jar'.
Possibly also verify that no other class files are present.

One way of doing this could be:

Reuse the list of spec that is defined under appserver/pom.xml, with a mojo in the spec-version-maven-plugin.

It would be similar to what we did to ensure all spec jars had compliant
metadata around the time of EE7/GFv4 release.

E.g. It could be an option to the current mojo "check-distribution", to check-up
a "class-path jar", or a separate mojo.

Possibly hook that by default in the build / CI job.






[GLASSFISH-540] maven javadoc cannot resolve JDK references Created: 04/Apr/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: marina vatkina Assignee: prasads
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 540
Status Whiteboard:

as9-na

Tags: 3_1-exclude

 Description   

Tested on the latest code in trunk in persistence-api:
% maven -o javadoc
...
[javadoc] Building tree for all the packages and classes...
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Basic.java:54:
warning - Tag @link: reference not found: java.math.BigInteger java.math.BigInteger
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Basic.java:54:
warning - Tag @link: reference not found: java.math.BigDecimal java.math.BigDecimal
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Basic.java:54:
warning - Tag @link: reference not found: java.sql.Date java.sql.Date
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Basic.java:54:
warning - Tag @link: reference not found: java.sql.Time java.sql.Time
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Basic.java:54:
warning - Tag @link: reference not found: java.sql.Timestamp java.sql.Timestamp
[javadoc]
/faith4/gf/glassfish/persistence-api/src/java/javax/persistence/Version.java:64:
warning - Tag @link: reference not found: java.sql.Timestamp Timestamp



 Comments   
Comment by dpatil [ 05/Apr/06 ]

Email Conversation with Prasad:

As per the scope of javadocs, we would generate javadocs from sources ,
internally. For folks on glassfish.dev.java.net , we would be staging these
generated javadocs. Hence generating javadocs from modules in Glassfish is not
supported.

Try following to generate javadocs from appserv module where Prasad may have
fixed this issue already.
> cvs co appserv
> cd appserv; maven checkout bootstrap javadoc | tee log

This should generate correct javadocs for all modules including source and
binary modules. log file in above commands should not show those warning msgs.

Also I just confirmed it by running above command and no warning messages in
persistence-api module, although there are still 217 warning messages in other
modules which needs to be fixed.

Assigning it to Prasad for further fixes.

Comment by dpatil [ 05/Apr/06 ]

Need to fix the rest of the warning and variable $

{s1as-javadocs.publish.home}
value.

[copy] Copying 31 files to
/export/tinderbox/dinesh/ws45/m_jws/appserv/${s1as-javadocs.publish.home}

/javax/xml/registry/images

Comment by dpatil [ 05/Apr/06 ]

Assigning it to Prasad

Comment by marina vatkina [ 05/Apr/06 ]

Internal generation of javadocs is not an option for an open source project.
It should be possible to generate javadocs from each GlassFish module.

Comment by tcng [ 28/Apr/06 ]

related to build infrastructure

Comment by gfbugbridge [ 26/Jun/06 ]

<BT6443394>

Comment by sridatta [ 15/May/07 ]

Not a v2 stopper

Comment by prasads [ 07/Oct/10 ]

Excluding these issues from v3.1

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-987] Every promotion should post checksums information for all the jar files. Created: 22/Aug/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.0peur1
Fix Version/s: not determined

Type: Improvement Priority: Minor
Reporter: Homer Yau Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: FreeBSD
Platform: All
URL: https://glassfish.dev.java.net/downloads/v2-b13.html


Issuezilla Id: 987

 Description   

Every promotion should post checksums information for all the jar files.

For every promoted build, it should post those jar binary file checksums
information.

Checksums information should include "Filename","Size","MD5","SHA256"

It would prevent and detect any courrupt jar files during download.

-hyau



 Comments   
Comment by dpatil [ 12/Mar/07 ]

We have the Filename and size at download location, that should be sufficient to
see if the downloaded file is corrupted. downgrading to P4.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1254] Can't build with -Dmodules ... Created: 05/Oct/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: km105526 Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,254

 Description   

The build document at
https://glassfish.dev.java.net/public/BuildGlassFish.html#Complete_Instructions_on_how_to_Build
says that one can build using

-Dmodules=required modules.

This does not work with -Dmodules=admin-cli, appserv-commons etc. because
admin-cli build depends on appserv-docs So, one must check out appserv-docs
and build it from source.



 Comments   
Comment by gfbugbridge [ 21/Jan/07 ]

<BT6515670>

Comment by dpatil [ 12/Mar/07 ]

yes, this is known issue. current build structure doesn't resolve inter-module
dependencies. downgrading to P4 as build issue.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1478] Upgrade dbschema to newer version Created: 10/Nov/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: mf125085 Assignee: raccah
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File HowToStageCMPLibInGF.txt    
Issuezilla Id: 1,478

 Description   

The dbschema library shipping w/ glassfish originated from netbeans 5.0-beta2.
For glassfish 9.2, we should integrate a never version, probably slitting
dbschema.jar into a UI- and a runtime part. I've tested this w/ dbschema.jar
from netbeans 5.5 fcs, but ran into the following problem:

The CMP appserver tests, that do auto-capture schema, fail. The reason for the
failures always is that the captured schema doesn't contain a table required by
the beans. Might be a case mis-match issue btw. DDL script and
sun-cmp-mappings.xml, but if I adjust the DDL, the test I investigated still
fails w/ the same error.



 Comments   
Comment by mf125085 [ 10/Nov/06 ]

Created an attachment (id=584)
Steps for integrating dbschema.jar into glassfish

Comment by raccah [ 13/Nov/06 ]

Note: This task came out of issue 1176.

Comment by gfbugbridge [ 21/Jan/07 ]

<BT6515673>

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-1914] Cannot compile on Java 6 SDK Created: 05/Jan/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: markuskarg Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 1,914

 Description   

Since Java 6 is the current official standard, I treat it as a bug that GF
cannot be built using Java 6 SDK.



 Comments   
Comment by dpatil [ 17/Jan/07 ]

What's the compiler error you are referring to?
For GlassFish V2, we are supporting JDK 6 runtime. If we can resolve binary
dependencies like WSIT (which seems to be resolved now) to compile with JDK 6
then we can get GlassFish also compile with JDK 6.

Comment by gfbugbridge [ 21/Jan/07 ]

<BT6515678>

Comment by dpatil [ 12/Mar/07 ]

this is not requirement for this release, so downgrading to P4.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-2544] -target 1.5 is missing Created: 03/Mar/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: markuskarg Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,544

 Description   

I am using JDK 6 to compile GlassFish. Unfortunately there is no "-target 1.5"
is the build.xml of e. g. entity-persistence. So often it happens that I forget
to explicitely set JAVA_HOME=C:\....\jdk1.5 before running ant. As a result,
the entity-persistence-tests cannot run the tests because the do not expect the
binaries of beeing in -target 1.6 mode...

So it would be really great if you would add "-target 1.5" into all build.xml
files, so that the compiler will produce Java EE 1.5 compliant binaries always.



 Comments   
Comment by dpatil [ 26/Mar/07 ]

Current GlassFish version doesn't compile with JDK1.6, there is no such
requirement for V2 at least. So downgrading to P4.

Comment by gfbugbridge [ 05/Apr/07 ]

<BT6543246>

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3490] appserv-docs build.xml ignores maven.repo.local settings from ~/build.properties Created: 10/Aug/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Sanjeeb Sahoo Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,490
Status Whiteboard:

as91-na,as91ur1-na


 Description   

Although I set maven.repo.local=/space/ss141213/mavenrep in my
~/build.properties, the following error message indicates that appserv-docs
build scripts ignores my settings. They are expecting the maven local repository
to be in the default location, i.e.,
/space/ss141213/WS/RTAS.proto/glassfish_dependencies/.

invoke-ant:
[java] Buildfile:
/space/ss141213/WS/RTAS.proto/glassfish/bootstrap/../../glassfish/bootstrap/../../glassfish/appserv-docs/build.xml
[java]
[java] post-bootstrap:
[java]
[java] do.unzip:
[java] [echo]
/space/ss141213/WS/RTAS.proto/glassfish/appserv-docs/../../glassfish_dependencies
Unzipping glassfish-help-20070803.jar to ./build
[java] [unzip] Expanding:
/space/ss141213/WS/RTAS.proto/glassfish_dependencies/glassfish-help/jars/glassfish-help-20070803.jar
into /space/ss141213/WS/RTAS.proto/glassfish/appserv-docs/build
[java]
[java] BUILD FAILED
[java] /space/ss141213/WS/RTAS.proto/glassfish/appserv-docs/build.xml:97:
The following error occurred while executing this line:
[java] /space/ss141213/WS/RTAS.proto/glassfish/appserv-docs/build.xml:107:
Error while expanding
/space/ss141213/WS/RTAS.proto/glassfish_dependencies/glassfish-help/jars/glassfish-help-20070803.jar
[java]
[java] Total time: 0 seconds



 Comments   
Comment by gfbugbridge [ 10/Aug/07 ]

<BT6591885>

Comment by Dhiru Pandey [ 14/Aug/07 ]

Not a release stopper for 9.1

Comment by dpatil [ 06/Nov/07 ]

yes this is obvious behaviour as we use maven reactor to download the binaries
which loads bootstrap/project.properties before other property files.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3908] maven bootstrap checkout build -Dmodules=appserv-core fails Created: 11/Dec/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Sanjeeb Sahoo Assignee: raharsha
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,908
Status Whiteboard:

as91ur1-na


 Description   

I am trying to run
maven bootstrap checkout build -Dmodules=appserv-core

It fails with following error:
[java] assemble:
[java] [copy] Copying 68 files to
/space/ss141213/WS/gf/v2ur1/glassfish/appserv-core/build
[java] [jar] Updating jar:
/space/ss141213/WS/gf/v2ur1/publish/glassfish/lib/appserv-admin.jar
[java] [jar] Updating jar:
/space/ss141213/WS/gf/v2ur1/publish/glassfish/lib/appserv-deployment-client.jar
[java] [jar] Updating jar:
/space/ss141213/WS/gf/v2ur1/publish/glassfish/lib/appserv-rt.jar
[java]
[java] BUILD FAILED
[java] /space/ss141213/WS/gf/v2ur1/glassfish/appserv-core/build.xml:155:
/space/ss141213/WS/gf/v2ur1/glassfish/jacc-provider/build not found.
[java]
[java] Total time: 1 minute 51 seconds
[java] [ERROR] Java Result: 1

It is failing because appserv/build.xml tries to jar classes from
../jacc-provider/build directory which is not there as I am not building that
module. This bug is caused by the following change:
http://fisheye5.cenqua.com/browse/~br=SJSAS91_FCS_BRANCH/glassfish/appserv-core/build.xml?r1=1.24&r2=1.24.6.1

Suggested Fix:
--------------
Move the code that is populating policy classes in appserv-launcher.jar from
appserv-core/build.xml to jacc-provider/build.xml.



 Comments   
Comment by basler [ 11/Dec/07 ]

Not a 91ur1 release stopper

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-3909] GlassFish build does not work if maven local repo is outside the source tree Created: 11/Dec/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Sanjeeb Sahoo Assignee: dpatil
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 3,909
Status Whiteboard:

as91ur1-na


 Description   

In my ~/build.properties, I set
maven.repo.local=/space/ss141213/mavenrep

Yet, I found glassfish/appserv-docs module trying to locate some dependencies
from glassfish_dependencies directory in my workspace directory. It ignores the
value specified in my ~/build.properties, because appserv-docs/build.xml does
not import settings from that file.

Patch:
------
Index: build.xml
===================================================================
RCS file: /cvs/glassfish/appserv-docs/build.xml,v
retrieving revision 1.11
diff -r1.11 build.xml
41a42
> <property file="$

{user.home}

/build.properties"/>



 Comments   
Comment by basler [ 11/Dec/07 ]

Not a 91ur1 release stopper

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5447] mvn -U install fails to download jars or inifitely loops to reload them Created: 08/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: ne110415 Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,447
Status Whiteboard:

gfv3-prelude-excluded


 Description   

.../v3> mvn -U install
fails to either download maven jars or loops inifitely while reloading them.

Please see the gf@dev thread: https://glassfish.dev.java.net/servlets/ReadMsg?
list=dev&msgNo=8273



 Comments   
Comment by raih [ 11/Aug/08 ]

will keep this open until we know exactly why this spinning happens.

Comment by kumara [ 19/Aug/08 ]

Add gfv3-prelude-include to status whiteboard

Comment by kumara [ 03/Sep/08 ]

v3 defect tracking

Comment by raih [ 05/Sep/08 ]

very interesting problem. Will come back when we get additional resources

Comment by kumara [ 08/Sep/08 ]

Not must have for prelude

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5495] Unable to download parent artifacts for v3/ejb/ejb-api some times Created: 14/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: raih Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 5,495
Status Whiteboard:

gfv3-prelude-included


 Description   

This bug has been filed to do the postmortem analysis on what is going on behind
scenes during maven build for the case of a) giving repo list in the
settings.xml and for the case b) No settings.xml at all.

The following is seen in v3 build for certain configuration of ejb/ejb-api
during the very beginning stage of mvn install:

+ Error stacktraces are turned on.
Maven version: 2.0.4
[DEBUG] Building Maven user-level plugin registry from: '/home/hg120123/.m2/plugin
-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: '/net/harshag/space/rai/
maven2.0/maven-2.0.4/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM: org.glassfish.api:api::2.0-SNAPSHOT of project:
javax.ejb:ejb-alpha:jar:3.1-SNAPSHOT in relative path: ../pom.xml
[DEBUG] Invalid parent-POM referenced by relative path '../pom.xml' in parent spec
ification in javax.ejb:ejb-alpha:jar:3.1-SNAPSHOT:
Specified: org.glassfish.api:api::2.0-SNAPSHOT
Found: org.glassfish.ejb:ejb:pom:null
[DEBUG] Retrieving parent-POM: org.glassfish.api:api::2.0-SNAPSHOT for project:
javax.ejb:ejb-alpha:jar:3.1-SNAPSHOT from the repository.
[DEBUG] Skipping disabled repository central
[DEBUG] api: using locally installed snapshot
[DEBUG] Skipping disabled repository central
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.glassfish.api
ArtifactId: api
Version: 2.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

org.glassfish.api:api:pom:2.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.glassfis
h.api:api for project: javax.ejb:ejb-alpha:jar:3.1-SNAPSHOT
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find arent:
org.glassfish.api:api for project: javax.ejb:ejb-alpha:jar:3.1-SNAPSHOT
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1161)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:674)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.glassfish.a
pi:api' not found in repository: Unable to download the artifact from any repository

org.glassfish.api:api:pom:2.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:513)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1157)
... 17 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository

org.glassfish.api:api:pom:2.0-SNAPSHOT

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467)
... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
ownload the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124)
... 20 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Aug 14 11:58:38 PDT 2008
[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------



 Comments   
Comment by kumara [ 19/Aug/08 ]

Add gfv3-prelude-include to status whiteboard

Comment by kumara [ 03/Sep/08 ]

v3 defect tracking

Comment by raih [ 05/Sep/08 ]

very difficult to catch this bug

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5500] Failed to resolve artifact: org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:distribution-fragment:10.0-SNAPSHOT Created: 14/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: raih Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 5,500
Status Whiteboard:

gfv3-prelude-excluded


 Description   

Mr.Hudson is not happy some times and hence shows up the following:

[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from maven2-repository.dev.java.net
[DEBUG] repository metadata for: 'snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT' could not
be found on repository: maven2-repository.dev.java.net
[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from glassfish-repository-wsinterop
[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from java-dev-repository
[DEBUG] repository metadata for: 'snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT' could not
be found on repository: java-dev-repository
[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from repo1.maven.org
[DEBUG] repository metadata for: 'snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT' could not
be found on repository: repo1.maven.org
[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from maven2.java.net
[DEBUG] repository metadata for: 'snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT' could not
be found on repository: maven2.java.net
[INFO] snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT: checking
for updates from maven2.java.net-backup
[DEBUG] repository metadata for: 'snapshot
org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT' could not
be found on repository: maven2.java.net-backup
[DEBUG] Skipping disabled repository central
[DEBUG] jdbc-ra: using locally installed snapshot
[DEBUG] Trying repository glassfish-repository-wsinterop
[ant] Exiting
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml.
[HUDSON] Archiving
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\pom.xml to
/files/hudson/server/jobs/glassfish-v3-windows/modules/org.glassfish.distributions$web/builds/2008-08-14_11-14-12/archive/org.glassfish.distributions/web/10.0-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An Ant BuildException has occured: The following error occurred while
executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:142: The
following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]

http://maven.dyndns.org/glassfish/org/glassfish/jdbc/jdbc-ra/jdbc-ra-distribution/jdbc-ra/10.0-SNAPSHOT/jdbc-ra-10.0-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException
has occured: The following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:142: The
following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:42)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:133)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:139)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:543)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:489)
at hudson.remoting.UserRequest.perform(UserRequest.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:23)
at hudson.remoting.Request$2.run(Request.java:200)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant BuildException
has occured: The following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:142: The
following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]
at
org.jvnet.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:130)
at org.jvnet.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:176)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:159)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 28 more
Caused by: The following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:142: The
following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.jvnet.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:117)
... 32 more
Caused by:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:142: The
following error occurred while executing this line:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:380)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
... 36 more
Caused by:
C:\hudson\workspace\glassfish-v3-windows\v3\distributions\web\build.xml:95:
Failed to resolve artifact.
Trail=[org.glassfish.distributions:web:10.0-SNAPSHOT--(compile)-->org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:10.0-SNAPSHOT]
at org.jvnet.maven.plugin.antrun.ResolveAllTask.execute(ResolveAllTask.java:129)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:378)
... 44 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to locate resource in repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file
-DgroupId=org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution -DartifactId=jdbc-ra \
-Dversion=10.0-SNAPSHOT -Dpackaging=distribution-fragment
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file
-DgroupId=org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution -DartifactId=jdbc-ra \
-Dversion=10.0-SNAPSHOT -Dpackaging=distribution-fragment
-Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]

org.glassfish.jdbc.jdbc-ra.jdbc-ra-distribution:jdbc-ra:distribution-fragment:10.0-SNAPSHOT

from the specified remote repositories:
maven2.java.net (http://download.java.net/maven/2),
repo1.maven.org (http://repo1.maven.org/maven2),
maven2.java.net-backup (https://maven2-repository.dev.java.net/nonav/repository),
glassfish-repository-wsinterop (http://maven.dyndns.org/glassfish/),
glassfish-repository (http://download.java.net/maven/glassfish),
maven2-repository.dev.java.net (http://download.java.net/maven/2/),
central (http://repo1.maven.org/maven2),
java-dev-repository (https://maven-repository.dev.java.net/nonav/repository)

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:197)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73)
at
org.jvnet.maven.plugin.antrun.MavenComponentBag.resolveArtifact(MavenComponentBag.java:313)
at
org.jvnet.maven.plugin.antrun.DependencyGraph$Node$1.resolve(DependencyGraph.java:376)
at
org.jvnet.maven.plugin.antrun.DependencyGraph$Node.getArtifactFile(DependencyGraph.java:456)
at org.jvnet.maven.plugin.antrun.ResolveAllTask.resolve(ResolveAllTask.java:146)
at org.jvnet.maven.plugin.antrun.ResolveAllTask.execute(ResolveAllTask.java:121)
... 50 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
locate resource in repository
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:100)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:94)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:446)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:347)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:181)
... 56 more
Caused by: java.io.FileNotFoundException:
http://maven.dyndns.org/glassfish/org/glassfish/jdbc/jdbc-ra/jdbc-ra-distribution/jdbc-ra/10.0-SNAPSHOT/jdbc-ra-10.0-SNAPSHOT.zip
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83)
... 60 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 32 minutes 32 seconds
[INFO] Finished at: Thu Aug 14 11:46:57 PDT 2008
[INFO] Final Memory: 87M/155M
[INFO] ------------------------------------------------------------------------



 Comments   
Comment by kumara [ 19/Aug/08 ]

Add gfv3-prelude-include to status whiteboard

Comment by kumara [ 20/Aug/08 ]

dpatil->raih till I find someone to investigate this.

Comment by kumara [ 03/Sep/08 ]

v3 defect tracking

Comment by raih [ 05/Sep/08 ]

...

Comment by kumara [ 08/Sep/08 ]

Not must have for Prelude

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5501] consolidate artifact repositories and plugin repositories Created: 14/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: raih Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 5,501
Status Whiteboard:

gfv3-prelude-excluded


 Description   

Re-org artifact repositories and plugin repositories in v3



 Comments   
Comment by kumara [ 19/Aug/08 ]

Add gfv3-prelude-include to status whiteboard

Comment by kumara [ 03/Sep/08 ]

v3 defect tracking

Comment by raih [ 05/Sep/08 ]

Need to clean up repo list in the code and as well as the destination repos.

Comment by kumara [ 08/Sep/08 ]

Not must have for Prelude

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-5645] mvn 2.0.8 updates repository with old binaries Created: 26/Aug/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Shalini Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 5,645
Status Whiteboard:

gfv3-prelude-excluded


 Description   

mvn version used : 2.0.8

Reproducing Problem :
---------------------
svn update
mvn clean install

This updates the repository with 0.3.15 hk2 binaries as well as 0.3.8 binaries
thereby updating the distribution web.zip with 0.3.8 binaries. As a result start
up of domain fails.

This is apparent when i did a mvn -X install > bld.log 2>&1. The bld.log shows
some snippets like

[DEBUG] com.sun.enterprise:hk2:jar:0.3.15:provided (removed - nearer found: 0.3.8)
[DEBUG] com.sun.enterprise:hk2:jar:0.3.8:provided (selected for provided)
[DEBUG] com.sun.enterprise:hk2-core:jar:0.3.8:provided (selected for provided)
[DEBUG] com.sun.enterprise:config:jar:0.3.8:provided (selected for provided)
[DEBUG] com.sun.enterprise:auto-depends:jar:0.3.8:provided (selected for
provided)

Clearing the repository and building the workspace afresh did not help.

Workaround :
------------
Using maven 2.0.7 solves the problem.



 Comments   
Comment by kumara [ 28/Aug/08 ]

Change to status whiteboard for v3 bug tracking

Comment by kumara [ 03/Sep/08 ]

dpatil->raih

Comment by raih [ 05/Sep/08 ]

A maven bug? Didn't get a chance to look into this issue.

Due to this bug, we will not recommend maven 2.0.8 for Gfv3 (until we know why
it does what it does).

Gfv3 Docs: Need to mention this or say minimal system configuration, needed
toos / maven versions etc. ?

Comment by kumara [ 08/Sep/08 ]

Not must have for prelude

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-6611] Unnecessary checked in src/main/resources/META-INF/MANIFEST.MF files Created: 22/Oct/08  Updated: 09/Nov/10

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: future release

Type: Bug Priority: Minor
Reporter: marina vatkina Assignee: janey
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 6,611
Status Whiteboard:

gfv3-prelude-excluded


 Description   

All (most?) javax.xxx modules have empty src/main/resources/META-INF/MANIFEST.MF
checked in into the src tree. Only javax.ejb seems to need it (because 'jar'goal
doesn't know about a different manifest file created by the felix plugin).



 Comments   
Comment by marina vatkina [ 22/Oct/08 ]

Not for prelude

Comment by kumara [ 24/Oct/08 ]

Reclassifying as P4 because these issues are not must fix for prelude release.
This issue will be scrubbed after prelude release and will be given the right
priority for v3 final release.

Comment by marina vatkina [ 30/Oct/08 ]

If we want to remove src/main/resources/META-INF/MANIFEST.MF in javax.ejb, the
following changes in the pom.xml seem to allow it:
Index: javax.ejb/pom.xml
===================================================================
— javax.ejb/pom.xml (revision 23609)
+++ javax.ejb/pom.xml (working copy)
@@ -83,7 +83,7 @@
plugin in creating manifest file entries for an embedded
dependencies
-->

  • <manifestLocation>$ {pom.build.directory}

    </manifestLocation>
    +
    <manifestLocation>$

    {project.build.outputDirectory}</manifestLocation>

    <!-- Maven uses the output directory (target/classes)
    rather than the final bundle, when compiling against
    @@ -104,6 +104,14 @@
    </execution>
    </executions>
    </plugin>
    + <plugin>
    + <artifactId>maven-jar-plugin</artifactId>
    + <configuration>
    + <archive>
    +
    <manifestFile>${project.build.outputDirectory}

    /MANIFEST.MF</manifestFile>
    + </archive>
    + </configuration>
    + </plugin>
    </plugins>
    </build>

Comment by Sanjeeb Sahoo [ 09/Nov/10 ]

will look into it in future.





[GLASSFISH-7032] unsupported class version in build Created: 13/Jan/09  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: sankarpn Assignee: raih
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 7,032

 Description   

B60F

1. Installed the SGES EE build with packaged JDK
2. created and started a 2 instance cluster, the following errors were thrown

[2009-01-13T19:11:46.18] # Actual:
/usr/sankar/ws/snmp/appservereeb60f/bin/asadmin start-cluster --user admin
--passwordfile
/usr/sankar/ws/snmp/appserver-sqe/se/admincli/config/runtime/sepassword.txt
--host localhost --port 4849 sa_cluster1
[2009-01-13T19:11:46.18] The clustered instance, sa_cluster1_server1, was
successfully started.
[2009-01-13T19:12:12.17] error 0
[#|2009-01-13T11:11:59.485-0800|WARNING|sun-appserver2.1|javax.jms|_ThreadID=10;_ThreadName=main;_RequestID=e33869ab-27e6-4323-88db-baa2a16d80a6;|[C4003]:
Error occurred on connection creation [localhost:37676]. - cause:
java.net.ConnectException: Connection refused|#]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17] error 1
[#|2009-01-13T11:12:02.525-0800|WARNING|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=10;_ThreadName=main;TimerBean;_RequestID=e33869ab-27e6-4323-88db-baa2a16d80a6;|EJB5108:Unable
to initialize EJB Timer Service. The likely cause is the database has not been
started or the timer database table has not been created.|#]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17] error 2
[#|2009-01-13T11:12:02.973-0800|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|ThreadID=10;_ThreadName=main;_CallFlowPool;_RequestID=e33869ab-27e6-4323-88db-baa2a16d80a6;|RAR5005:Error
in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17] The clustered instance, sa_cluster1_server2, was
successfully started.
[2009-01-13T19:12:12.17] error 0
[#|2009-01-13T11:12:34.180-0800|WARNING|sun-appserver2.1|javax.jms|_ThreadID=10;_ThreadName=main;_RequestID=08ad389f-b429-41eb-ac61-aafff4837c35;|[C4003]:
Error occurred on connection creation [localhost:37676]. - cause:
java.net.ConnectException: Connection refused|#]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17] error 1
[#|2009-01-13T11:12:38.161-0800|SEVERE|sun-appserver2.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=08ad389f-b429-41eb-ac61-aafff4837c35;|core.unexpected_error_occured_while_loading_system_app
[2009-01-13T19:12:12.17] java.lang.UnsupportedClassVersionError:
UnsupportedClassVersionError: Class
com.sun.ejb.containers.TimerMigrationBean649625130_ConcreteImpl has unsupported
major or minor version numbers, which are greater than those found in the Java
Runtime Environment version 1.5.0_14
[2009-01-13T19:12:12.17] at
com.sun.enterprise.loader.EJBClassLoader.findClass(EJBClassLoader.java:691)
[2009-01-13T19:12:12.17] at
java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[2009-01-13T19:12:12.17] at
java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[2009-01-13T19:12:12.17] at
com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:423)
[2009-01-13T19:12:12.17] at
com.sun.ejb.containers.EntityContainer.<init>(EntityContainer.java:246)
[2009-01-13T19:12:12.17] at
com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:332)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:527)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.java:191)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:126)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.ExtendedApplicationLoader.doLoad(ExtendedApplicationLoader.java:134)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:238)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.AbstractManager.loadOneSystemApp(AbstractManager.java:407)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.AbstractManager$SystemAppStarter.doRun(AbstractManager.java:664)
[2009-01-13T19:12:12.17] at
com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
[2009-01-13T19:12:12.17] at
com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
[2009-01-13T19:12:12.17] at
com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:210)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.AbstractManager.loadSystem(AbstractManager.java:331)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.SystemAppLifecycle.loadSystemApps(SystemAppLifecycle.java:162)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:108)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:446)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:134)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.PEMain.run(PEMain.java:409)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.PEMain.main(PEMain.java:336)
[2009-01-13T19:12:12.17] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2009-01-13T19:12:12.17] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[2009-01-13T19:12:12.17] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[2009-01-13T19:12:12.17] at java.lang.reflect.Method.invoke(Method.java:585)
[2009-01-13T19:12:12.17] at
com.sun.enterprise.server.PELaunch.main(PELaunch.java:415)
[2009-01-13T19:12:12.17] |#]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17]
[2009-01-13T19:12:12.17] error 2
[#|2009-01-13T11:12:38.976-0800|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|ThreadID=10;_ThreadName=main;_CallFlowPool;_RequestID=08ad389f-b429-41eb-ac61-aafff4837c35;|RAR5005:Error
in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]
[2009-01-13T19:12:12.22]
[2009-01-13T19:12:12.22]
[2009-01-13T19:12:12.22] Command start-cluster executed successfully.



 Comments   
Comment by marina vatkina [ 13/Jan/09 ]

Did you start that instance (or DAS) that reports the class version mismatch,
first with JDK 6?

Comment by sankarpn [ 13/Jan/09 ]

No, I am getting the error the very first time I am starting this cluster which
has 2 instances in it.

Comment by harpreet [ 16/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-8057] Fix build warnings coming from maven-bundle-plugin Created: 28/Apr/09  Updated: 11/Mar/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: V3
Fix Version/s: future release

Type: Bug Priority: Minor
Reporter: Sanjeeb Sahoo Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 8,057

 Description   

During v3 build, because of the way we configure maven-bundle-plugin, we get
following warnings:

[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.

[WARNING] Warning in manifest for org.glassfish:javax.xml.soap:jar:3.0-SNAPSHOT
: Superfluous export-package instructions: [javax.xml.soap.*]
[WARNING] Warning in manifest for org.glassfish:javax.xml.soap:jar:3.0-SNAPSHOT
: Did not find matching referal for *

[WARNING] Ignoring project type pom - supportedProjectTypes = [hk2-jar, bundle]

[WARNING] Ignoring project type distribution-fragment - supportedProjectTypes =
[hk2-jar, bundle]

[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Superfluous
export-package instructions: [*]
[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not find
matching referal for !com.sun.jndi.ldap
[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not find
matching referal for !com.sun.jndi.toolkit.corba
[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not find
matching referal for !com.sun.security.sasl.preview
[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not find
matching referal for !com.sun.security.sasl.util
[WARNING] Warning in manifest for
org.glassfish.external:ldapbp-repackaged:jar:3.0-SNAPSHOT : Did not find
matching referal for *


None of them affect the build, but it is better to fix them for people who pay
attention to WARNINGs emitted by a build.



 Comments   
Comment by Sanjeeb Sahoo [ 28/Apr/09 ]

assigned to self

Comment by Sanjeeb Sahoo [ 28/Sep/09 ]

Not all the warnings mentioned in this bug note are caused by
maven-bundle-plugin, but yes, some do. In any case, this is not a p3, as we know
the build is fine. So, p3->p4

Comment by Sanjeeb Sahoo [ 09/Nov/10 ]

-> 3.2





[GLASSFISH-17533] When building v3, executing "create-domain" task failed Created: 31/Oct/11  Updated: 31/Oct/11

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: v3.0.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: TangYong Assignee: janey
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days
Environment:

■OS
Windows XP SP3 JP
■JDK Version
1.6.0_20-b02
■ Maven Version
Maven 2.2.1
■ Glassfish V3 Version
v3.0 b74b


Attachments: Text File build_failure(create-domain).txt     Text File build_success(create-domain).txt    
Tags: create-domain

 Description   

When I build glassfish v3.0(b74.2) from https://svn.java.net/svn/glassfish~svn/tags/3.0-b74b,
I met a curious problem as following:

1) Making a building workspace
The building workspace's directory name is: F:\GlassfishV3\v3(b74b)

2) cd the building workspace, and execute the following command:
mvn -Dmaven.repo.local=F:\GlassfishV3\mavenrepo\glassfishv3 install

3) When executing "create-domain" task, the building process failed,
-------------------------------------------------------------------------------
...
create-domain:
[echo] Directory to run command from: F:\GlassfishV3\v3(b74b)\distributions\nucleus/target/stage/glassfishv3/glassfish/bin
[echo] Command to run: F:\GlassfishV3\v3(b74b)\distributions\nucleus/target/stage/glassfishv3/glassfish/bin/asadmin.bat
[exec] 'F:\GlassfishV3\v3\' は、内部コマンドまたは外部コマンド、
[exec] 操作可能なプログラムまたはバッチ ファイルとして認識されていません。
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
...
--------------------------------------------------------------------------------

About the whole building process,please see the log file(build_failure(create-domain).txt).

In addition, after I changed the building workspace's directory name into "F:\GlassfishV3\v3\b74b" ,
and executed the build again, the build process is successful(please see the log file(build_success(create-domain).txt)).

So, I think that building workspace's directory name with '()' can cause the problem.

--Best Regard
--Tang Yong






[GLASSFISH-19707] latest-glassfish-ml.zip (8/2/2013) reports version v4_b73 not v4_b76 when integrating with IntelliJ IDEA 12.0.4 Created: 21/Feb/13  Updated: 11/Apr/13

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b76_EE7MS5
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Mohamed Taman Assignee: vince kraemer
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

IntelliJ IDEA 12.0.4
Windows 7.


Tags: adoptajsr

 Description   

While integrating Glassfish latest ml (which released on 8/2/2013) to IntelliJ IDEA 12.0.4, when pointing to the glassfish home folder it detect it as v4_b73 while it should be v4_b76.



 Comments   
Comment by vince kraemer [ 11/Apr/13 ]

it looks like latest-glassfish-ml.zip is not getting updated 'in-sync' with the named bulds..

The current 'youngest named build' is b84 which was built on 10 Apr 2013. It looks like the build was not complete... there is only a glassfish-4.0-b84.zip. So, latest-glassfish-ml.zip looks like it is claiming that the b83 bits (glassfish-4.0-b83-ml.zip are the latest.

This can be confusing.

But there isn't anything the IDE can do if the repo is 'lying' to the user about the latest-ness of the latest-glassfish-ml.zip...

Comment by vince kraemer [ 11/Apr/13 ]

pushed issue to build_system for further analysis.

Comment by Romain Grécourt [ 11/Apr/13 ]

What is this about ? Is this about version resolved by IntelliJ or download.java.net ?

Comment by Romain Grécourt [ 11/Apr/13 ]

download.java.net has some caching thing, b84 is well complete and the latest- files are well synched.

Comment by vince kraemer [ 11/Apr/13 ]

Hmm. ok.

FILER: is there still a disconnect between latest-glassfish-ml.zip and the identification that is displayed by IntelliJ?





[GLASSFISH-21264] maven source and javadoc is empty Created: 02/Dec/14  Updated: 02/Dec/14

Status: Open
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0, 4.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: wulcan Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

sources.jar and javadoc.jar contains neither sources nor javadocs

http://search.maven.org/#artifactdetails%7Corg.glassfish.main.extras%7Cglassfish-embedded-web%7C4.1%7Cjar

The artifacts on maven.java.net are empty too.



 Comments   
Comment by Romain Grécourt [ 02/Dec/14 ]

The embedded artifacts are currently built using some mixture of ant. These ubber jars don't have their corresponding ubber sources.jar and ubber javadoc.jar.
Mavenizing them properly would require addressing other packaging enhancements.





Generated at Sat Feb 28 13:14:33 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.