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

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

Type: Bug Priority: Major
Reporter: Joe Di Pol Assignee: trilokagarwal
Resolution: Fixed 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-21321] JDK9 - Need to update felix.jar Created: 01/Mar/15  Updated: 06/Mar/15  Resolved: 06/Mar/15

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

Type: Task Priority: Major
Reporter: Arindam Bandyopadhyay Assignee: Arindam Bandyopadhyay
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-21236 Glassfish 4.1 won't start with JDK 9 ... Resolved

 Description   

If we want to run glassfish with JDK 9 , (refer GLASSFISH-21236) we need to update glassfish4/glassfish/osgi/felix/bin/felix.jar . I have patch the jar to make it JDK 9 compatable .However the jar is coming from the felix Maven repository . I have logged a felix bug FELIX-4808 to make Felix JDK 9 comparable . Until the bug is resolved , if we want to run glassfish with JDK 9 we need to place the patched jar in glassfish private repository and change the pom of main/nucleus/osgi-platforms/felix project to pick
up the jar from glassfish local repository instead of maven central repository.



 Comments   
Comment by Arindam Bandyopadhyay [ 06/Mar/15 ]

Felix update is not required . The issue can be fixed by adding the following entry in glassfish4/glassfish/config/osgi.properties.
org.osgi.framework.system.capabilities= \
${eecap-${java.specification.version}} eecap-1.9= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7,1.8,1.9"
eecap-1.8= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7,1.8"
eecap-1.7= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7"
eecap-1.6= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4,1.5,1.6"
eecap-1.5= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4,1.5"
eecap-1.4= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1,1.2", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3,1.4"
eecap-1.3= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2,1.3"
eecap-1.2= osgi.ee; osgi.ee="OSGi/Minimum"; version:List<Version>="1.0,1.1", \
osgi.ee; osgi.ee="JavaSE"; version:List<Version>="1.0,1.1,1.2"

Comment by Arindam Bandyopadhyay [ 06/Mar/15 ]

Closing the Task.





[GLASSFISH-20288] Make nucleus compile with Java source=1.7, target=1.7 Created: 11/Apr/13  Updated: 27/Feb/15  Resolved: 27/Feb/15

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b84_RC1
Fix Version/s: 4.1

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


 Description   

This issue is for changing nucleus to compile with Java source=1.7 and target=1.7.

I've tried this in a private workspace and passed the following test suites:

  • full top-down build of BG and CL
  • nucleus QL and admin devtests
  • GF QL
  • CPAS+BG admin devtests


 Comments   
Comment by michael.y.chen [ 24/Apr/13 ]

Tom, the main goal to enable this is to use the JDK 7 features to enhance performance. Given where we are, I don't think we have time to take advantage of the JDK 7 features now. To reduce risks, I think we should defer this to 4.0.1.

Comment by Tom Mueller [ 24/Apr/13 ]

Actually, this is a low risk fix. However, deferring to 4.0.1.

Comment by Romain Grécourt [ 27/Feb/15 ]
------------------------------------------------------------------------
r63234 | romain_grecourt | 2014-04-30 10:58:32 +0200 (Wed, 30 Apr 2014) | 1 line

use souce=1.7,target=1.7 in nucleus
------------------------------------------------------------------------




[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-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-21271] essin Created: 14/Dec/14  Updated: 15/Dec/14  Resolved: 15/Dec/14

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

Type: Bug Priority: Critical
Reporter: Essin Assignee: Joe Di Pol
Resolution: Invalid Votes: 0
Labels: maven
Remaining Estimate: 3 weeks
Time Spent: Not Specified
Original Estimate: 3 weeks
Environment:

Linux


Status Whiteboard:

Wiki

Tags: 3_1_1-approved

 Description   

member






[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.





[GLASSFISH-21098] GlassFish 4.x can't be built using jdk8 Created: 24/Jun/14  Updated: 23/Sep/14  Resolved: 23/Sep/14

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

Type: Bug Priority: Critical
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: build, jdk8
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by JSFTEMPLATING-47 Annotation processor don't implement ... Resolved

 Description   

There are a couple of changes to make:

  • bump ASM from 4.0 to 5.0.3 in the command-security-maven-plugin
  • address the following fix
    Index: appserver/deployment/dol/src/main/java/com/sun/enterprise/deployment/util/DOLUtils.java
    ===================================================================
    --- appserver/deployment/dol/src/main/java/com/sun/enterprise/deployment/util/DOLUtils.java	(revision 63378)
    +++ appserver/deployment/dol/src/main/java/com/sun/enterprise/deployment/util/DOLUtils.java	(working copy)
    @@ -425,7 +425,9 @@
         public static void readAlternativeRuntimeDescriptor(ReadableArchive appArchive, ReadableArchive embeddedArchive, Archivist archivist, BundleDescriptor descriptor, String altDDPath) throws IOException, SAXParseException {
             String altRuntimeDDPath = null;
             ConfigurationDeploymentDescriptorFile confDD = null;
    -        for (ConfigurationDeploymentDescriptorFile ddFile : sortConfigurationDDFiles(archivist.getConfigurationDDFiles(), archivist.getModuleType(), embeddedArchive)) {
    +        @SuppressWarnings("unchecked") 
    +        List<ConfigurationDeploymentDescriptorFile> archivistConfDDFiles = archivist.getConfigurationDDFiles();
    +        for (ConfigurationDeploymentDescriptorFile ddFile : sortConfigurationDDFiles(archivistConfDDFiles, archivist.getModuleType(), embeddedArchive)) {        
                 String ddPath = ddFile.getDeploymentDescriptorPath();
                 if (ddPath.indexOf(DescriptorConstants.WLS) != -1 && 
                     appArchive.exists(DescriptorConstants.WLS + altDDPath)) {
    
  • Remove every usage of apt, that include apt-maven-plugin which is used by console and console plugins. However the annotation processors used (from jsftemplating project) are not using javax.annotation.processing API but the old APT API which has been removed in JDK8. These processors need to be changed in order to allow building with JDK8. This imply a release of the jsftemplating project.


 Comments   
Comment by Romain Grécourt [ 01/Aug/14 ]

I have all the changes prepared locally. Will push them after the incoming release (4.1)

Comment by Sanjeeb Sahoo [ 11/Aug/14 ]

In the meanwhile, can we add an enforcement rule in pom.xml to not allow the build with JDK8?

Comment by Romain Grécourt [ 11/Aug/14 ]

done.

Comment by Romain Grécourt [ 23/Sep/14 ]

Project: glassfish
Repository: svn
Revision: 63676
Author: romain_grecourt
Date: 2014-09-23 11:04:45 UTC
Link:

Log Message:
------------
GLASSFISH-21098 - Allow GlassFish to be built with JDK8. Removed usage of APT and old ASM library (released new version of jsftemplating since its annotation processors are used by the console, and upgraded ASM in the command-security-maven-plugin)

Revisions:
----------
63676

Modified Paths:
---------------
trunk/main/appserver/admingui/common/pom.xml
trunk/main/appserver/admingui/web/pom.xml
trunk/main/appserver/admingui/core/pom.xml
trunk/main/appserver/admingui/jms-plugin/pom.xml
trunk/main/nucleus/pom.xml
trunk/main/appserver/admingui/updatecenter/pom.xml
trunk/main/appserver/osgi-platforms/glassfish-osgi-console-plugin/pom.xml
trunk/main/appserver/pom.xml
trunk/main/appserver/admingui/full/pom.xml
trunk/main/appserver/deployment/dol/src/main/java/com/sun/enterprise/deployment/util/DOLUtils.java
trunk/main/appserver/admingui/jca/pom.xml





[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-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-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-20981] Build failure because of invalid pom.xml Created: 13/Feb/14  Updated: 19/Sep/14  Resolved: 18/Feb/14

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

Type: Bug Priority: Blocker
Reporter: HASUNUMA Kenji Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 Professional (x86/x64), JDK7 Update 51, Maven 3.1.1


Tags: jax-ws, jaxb, pom

 Description   

When building GlassFish 4.0.1 build 4, the build process is failed with following message. It is because that the specified version of webservices and jaxb does not exist on Maven central repository.

the specified version of webservices in pom.xml is 2.3.1-b259 but latest version on the central is 2.3.1-b104. And jaxb in pom.xml is 2.2.8-b131017.0915 but latest on the central is 2.2.8-b01.

---- Error message #1 ----

[INFO] Common persistence code between JPA and CMP ....... SUCCESS [3.266s]
[INFO] GlassFish Core EJB container implementation ....... FAILURE [0.336s]
[INFO] Full EJB Container add-ons ........................ SKIPPED

(snip)

[INFO] GlassFish Project ................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 23:50.842s
[INFO] Finished at: Thu Feb 13 15:35:45 JST 2014
[INFO] Final Memory: 353M/494M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ejb-container: Could not resolve depen
dencies for project org.glassfish.main.ejb:ejb-container:glassfish-jar:4.0.1-b04
: Failure to find org.glassfish.metro:webservices-api-osgi:jar:2.3.1-b259 in htt
ps://maven.java.net/content/repositories/promoted/ was cached in the local repos
itory, resolution will not be reattempted until the update interval of jvnet-nex
us-promoted has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR] mvn <goals> -rf :ejb-container

---- Error message #2 ----

[INFO] GlassFish Web Services related modules ............ SUCCESS [0.175s]
[INFO] JSR-109 implementation to deploy Metro ............ FAILURE [6.597s]
[INFO] GlassFish Metro Glue Code ......................... SKIPPED

(snip)

[INFO] GlassFish Project ................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 41:45.594s
[INFO] Finished at: Thu Feb 13 15:42:19 JST 2014
[INFO] Final Memory: 461M/494M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jsr109-impl: Could not resolve depende
ncies for project org.glassfish.main.webservices:jsr109-impl:glassfish-jar:4.0.1
-SNAPSHOT: Failed to collect dependencies at com.sun.xml.bind:jaxb-osgi:jar:2.2.
8-b131017.0915: Failed to read artifact descriptor for com.sun.xml.bind:jaxb-osg
i:jar:2.2.8-b131017.0915: Could not transfer artifact com.sun.xml.bind:jaxb-osgi
:pom:2.2.8-b131017.0915 from/to jvnet-nexus-promoted (https://maven.java.net/con
tent/repositories/promoted/): peer not authenticated -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR] mvn <goals> -rf :jsr109-impl



 Comments   
Comment by Romain Grécourt [ 13/Feb/14 ]

update assignee, component.

We are aware of this issue, it will be fixed very soon.

Comment by Romain Grécourt [ 18/Feb/14 ]

Issue is resolved: a new metro version has been integrated into GlassFish, and the missing bits have been recovered on maven.java.net.





[GLASSFISH-20977] gf-client-module.jar is an OSGi bundle, but should not be Created: 10/Feb/14  Updated: 19/Sep/14  Resolved: 20/Aug/14

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

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

Tags: 4_0_1-approved, 4_0_1-reviewed, build, osgi

 Description   

Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.main.appclient.gf-client-module [67]: Unable to resolve 67.0: missing requirement [67.0] osgi.wiring.package; (osgi.wiring.package=org.jboss.weld.environment.se)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
at org.jvnet.hk2.osgiadapter.OSGiModuleImpl.start(OSGiModuleImpl.java:210)



 Comments   
Comment by Romain Grécourt [ 19/Aug/14 ]

removing the OSGi metadata, makes the bundle starts.

However, it's still installed and shows up as:

   83|Active     |    1|file:/Users/romano/workspaces/glassfish/main2/appserver/distributions/glassfish/target/stage/glassfish4/glassfish/modules/gf-client-module.jar (0.0.0)
Comment by Romain Grécourt [ 20/Aug/14 ]

We will instead make the org.jboss.weld.environment.se import optional to allow this bundle to be started.

Comment by Romain Grécourt [ 20/Aug/14 ]
Log Message:
------------
fix for GLASSFISH-20977


Revisions:
----------
63645


Modified Paths:
---------------
trunk/main/appserver/appclient/client/acc/osgi.bundle


Diffs:
------
Index: trunk/main/appserver/appclient/client/acc/osgi.bundle
===================================================================
--- trunk/main/appserver/appclient/client/acc/osgi.bundle	(revision 63644)
+++ trunk/main/appserver/appclient/client/acc/osgi.bundle	(revision 63645)
@@ -43,3 +43,12 @@
                         org.glassfish.appclient.client.acc; \
                         org.glassfish.appclient.client.acc.callbackhandler;
                         org.glassfish.appclient.common; version=${project.osgi.version}
+
+# GLASSFISH-20977
+# This bundle is an OSGi bundle for convenience.
+# However it needs org.jboss.weld.environment.se package, which isn't provided in GlassFish.
+# The result is a non start-able OSGi bundle.
+# Making this import optional.
+Import-Package: \
+                        org.jboss.weld.environment.se;resolution:=optional, \
+                        *




[GLASSFISH-20952] Failed to start OSGiModuleImpl running some webservices tests. Created: 14/Jan/14  Updated: 19/Sep/14  Resolved: 03/Feb/14

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

Type: Bug Priority: Major
Reporter: Dennis MacConnell Assignee: Michal Gajdos
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File server.log    
Issue Links:
Related
is related to JERSEY-2339 [GF] Failed to start OSGiModuleImpl r... Resolved

 Description   

I'm getting the following exception running some of the CTS webservices tests on the latest RI build (GlassFish 4.0 b94):

[2014-01-14T16:16:32.563-0500] [glassfish 4.0] [SEVERE] [] [javax.enterprise.system.tools.deployment.common] [tid: _ThreadID=89 _ThreadName=AutoDeployer] [timeMillis: 1389734192563] [levelValue: 1000] [[
Exception while invoking class org.glassfish.webservices.WebServicesDeployer load method
java.lang.RuntimeException: A MultiException has 2 exceptions. They are:
1. com.sun.enterprise.module.ResolveError: Failed to start OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.gf-client-module [7]], State = [NEW]
2. java.lang.IllegalStateException: Could not load descriptor SystemDescriptor(
implementation=org.glassfish.appclient.common.ACCAppClientArchivist
contracts=

{org.glassfish.appclient.common.ACCAppClientArchivist,com.sun.enterprise.deployment.archivist.Archivist}

scope=org.glassfish.hk2.api.PerLookup
qualifiers={}
descriptorType=CLASS
descriptorVisibility=NORMAL
metadata=Bundle-SymbolicName=

{org.glassfish.main.appclient.gf-client-module}

,Bundle-Version=

{4.0.0.b94}

rank=0
loader=OsgiPopulatorPostProcessor.HK2Loader(OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.gf-client-module [7]], State = [NEW],32460147)
proxiable=null
analysisName=null
id=38
locatorId=0
identityHashCode=29744355
reified=false)

at org.glassfish.webservices.WebServicesDeployer.load(WebServicesDeployer.java:814)
at org.glassfish.webservices.WebServicesDeployer.load(WebServicesDeployer.java:96)
at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:206)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:313)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:493)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:537)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:546)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1423)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1500(CommandRunnerImpl.java:108)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1762)
at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:164)
at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:595)
at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:482)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:410)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:401)
at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:233)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)



 Comments   
Comment by Sanjeeb Sahoo [ 15/Jan/14 ]

It's not an OSGi issue. There appears to be some issue in the module which is why a module is not getting resolved. One of the two exceptions mentioned in the log is com.sun.enterprise.module.ResolveError, but unfortunately HK2 subsystem has not printed the stack for this exception. So, I am assigning this to HK2 team to fix their code to print the stack for the first exception which is always the root cause of the problem. There after the issue can be reassigned based on the new information revealed by the stack.

Comment by Lukas Jungmann [ 15/Jan/14 ]

transferring to hk2 per last comment

Comment by Joe Di Pol [ 16/Jan/14 ]

This occurred after r63056, the Jersey 2.0 -> 2.0.1 update in the 4.0 branch.

Comment by Snjezana Sevo-Zenzerovic [ 22/Jan/14 ]

Attaching full server.log file from failed autodeployment on RI b94. Looks like HK2 is printing the whole stack after all.

Comment by Snjezana Sevo-Zenzerovic [ 22/Jan/14 ]

Relevant log snippet seems to be:

Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.glassfish.main.appclient.gf-client-module [67]: Unable to resolve 67.0: missing requirement [67.0] osgi.wiring.package; (osgi.wiring.package=org.jboss.weld.environment.se)
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
at org.jvnet.hk2.osgiadapter.OSGiModuleImpl.start(OSGiModuleImpl.java:210)

Still a mistery since the file content of the RI did not change between b93 and b94 and I am not aware of any changes to the build process or checkins that would affect osgi bundle definitions.

Comment by Snjezana Sevo-Zenzerovic [ 03/Feb/14 ]

By the process of elimination, issue had to be caused by Hudson build environment used to produce GF 4.0 b94. Build respin using the exact same 4.0 branch revision "fixed" the issue.





[GLASSFISH-20427] [regression] A distribution's dependencies are not optional Created: 29/Apr/13  Updated: 19/Jun/14  Resolved: 19/Jun/14

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b86_RC2
Fix Version/s: 4.1_b07

Type: Bug Priority: Critical
Reporter: Sanjeeb Sahoo Assignee: Romain Grécourt
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-19770 create feature-set pom to contain pac... Resolved
Tags: 4_0_1-reviewed

 Description   

See GLASSFISH-17170 where in we had marked all the dependencies of a distribution optional so that one could use a distribution without having to pull in all its dependencies. It seems changes trunk has reverted that fix. Pl fix it for 4.0.



 Comments   
Comment by Romain Grécourt [ 29/Apr/13 ]

I prefer to use intermediate poms, in order to cut the graph at distribution level, but still have a visible graph for inheritance between distributions.
I'm not sure to address that in 4.0

Comment by Romain Grécourt [ 02/May/13 ]

will fix it for 4.0.1

Comment by Sanjeeb Sahoo [ 02/May/13 ]

This should be fixed in 4.0.

Comment by Romain Grécourt [ 06/May/13 ]

Michael, please evaluate. I can come up with a fix for 4.0 if needed.

Comment by michael.y.chen [ 07/May/13 ]

This is a bug, but I don't consider it showstopper.

  • How likely is it that a customer will hit the bug?

Not very likely. This bug is only encountered by maven users consuming glassfish.zip as a maven dependency in their project. It does not impact our download bundles.

  • How severe is the customer impact?

Low. There is no loss of data or functionality. It is annoying that all dependencies are downloaded by maven, but functionally things work.

Is this a regression? Yes, the 3.X glassfish.zip artifact does not have this behavior. But I still claim that customer impact is not severe enough to warrant it being a showstopper.





[GLASSFISH-19770] create feature-set pom to contain packager dependencies Created: 05/Mar/13  Updated: 19/Jun/14  Resolved: 19/Jun/14

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b78
Fix Version/s: 4.1_b07

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

Issue Links:
Dependency
blocks GLASSFISH-20427 [regression] A distribution's depende... Resolved
Tags: build, maven, packaging

 Description   

Create intermediate feature-set poms that should contain packager dependencies.
The purpose of this is to be able to cut the maven graph at distribution level, in order to not force the maven downloading of all distro transitive dependencies (i.e. packages direct dependencies).

Those feature-set poms will have full visibilit on the maven graph and should be re-used for distribution inheritance.
Distribution pom should be used only for direct consumption (i.e. zip).



 Comments   
Comment by Romain Grécourt [ 19/Jun/14 ]

Sending appserver/distributions/glassfish/pom.xml
Sending appserver/distributions/minnow/pom.xml
Sending appserver/distributions/pom.xml
Sending appserver/distributions/web/pom.xml
Adding appserver/featuresets
Adding appserver/featuresets/glassfish
Adding appserver/featuresets/glassfish/pom.xml
Adding appserver/featuresets/minnow
Adding appserver/featuresets/minnow/pom.xml
Adding appserver/featuresets/pom.xml
Adding appserver/featuresets/web
Adding appserver/featuresets/web/pom.xml
Sending appserver/pom.xml
Sending appserver/web/cdi-api-fragment
Transmitting file data .........
Committed revision 63364.





[GLASSFISH-15132] maven repo cleanup Created: 04/Feb/09  Updated: 17/Apr/14  Resolved: 17/Apr/14

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

Type: Task Priority: Minor
Reporter: Jennifer Chou Assignee: Joe Di Pol
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 68

 Description   

I would also like to see that we remove old junk from embedded -
10.0-SNAPSHOT,
3.0-Prelude-SNAPSHOT,
3.0-SNAPSHOT,
and eventually 3.0-Prelude-Embedded-m2.

We should only have these three -
3.0-Prelude-Embedded-SNAPSHOT,
3.0-Prelude-Embedded-PROMOTED,
and 3.0-Prelude-Embedded (for final build)

Our java.net maven2 repository can be accessed via SVN, but not GlassFish
repository. Need to find out URL.

Need to find out how to remove artifacts from the maven repository.



 Comments   
Comment by Nazrul [ 05/Feb/09 ]

We should only remove the old junk under glassfish/org/glassfish/embedded.

Comment by janey [ 13/Dec/10 ]

If I remove:

10.0-SNAPSHOT,
3.0-Prelude-SNAPSHOT,
3.0-SNAPSHOT,
and eventually 3.0-Prelude-Embedded-m2.

will that break some old builds?

Comment by Joe Di Pol [ 22/May/13 ]

Assigning to Romain to see if this bug is still relevant.

Comment by Romain Grécourt [ 23/May/13 ]

which repo is that ?

Comment by Romain Grécourt [ 17/Apr/14 ]

This issue is outdated. It is most likely related to the old java.net m2 repo.





[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-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-20845] Unable to build 4.0.1-SNAPSHOT with Maven on Mountain Lion using Oracle Java7 Created: 03/Oct/13  Updated: 20/Oct/13  Resolved: 15/Oct/13

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

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

dwhitla@raptor:~/dev/contrib/projects/glassfish/trunk/main$ java -version
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

dwhitla@raptor:~/dev/contrib/projects/glassfish/trunk/main$ mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 18:44:56+1000)
Maven home: /usr/share/maven
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: utf-8
OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"

dwhitla@raptor:~/dev/contrib/projects/glassfish/trunk/main$ svn info
Path: .
Working Copy Root Path: /Users/dwhitla/dev/contrib/projects/glassfish/trunk/main
URL: https://svn.java.net/svn/glassfish~svn/trunk/main
Repository Root: https://svn.java.net/svn/glassfish~svn
Repository UUID: 6f3ba3e3-413c-0410-a8aa-90bee3ab43b5
Revision: 62773
Node Kind: directory
Schedule: normal
Last Changed Author: dtwelves
Last Changed Rev: 62773
Last Changed Date: 2013-10-03 01:37:07 +1000 (Thu, 03 Oct 2013)


Tags: dependency, maven, metro

 Description   

Following the directions provided at https://wikis.oracle.com/display/GlassFish/FullBuildInstructions, and with an initially empty local Maven repository, I am unable to build Glassfish from a clean checkout of the source trunk as at revision 62773.
Using "mvn clean install", the build fails while attempting to satisfy dependencies of the "ejb-container" child module.
Specifically:

[ERROR] Failed to execute goal on project ejb-container: Could not resolve dependencies for project org.glassfish.main.ejb:ejb-container:glassfish-jar:4.0.1-SNAPSHOT: Could not find artifact org.glassfish.metro:webservices-api-osgi:jar:2.3.1-b111 in maven-central (http://repo1.maven.org/maven2/) -> [Help 1]

Both the POM and JAR are unavailable and it is not clear if or where the source for this dependency might reside within the glassfish~svn repository:

[INFO] ------------------------------------------------------------------------
[INFO] Building GlassFish Core EJB container implementation 4.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/org/glassfish/metro/webservices-api-osgi/2.3.1-b111/webservices-api-osgi-2.3.1-b111.pom
[WARNING] The POM for org.glassfish.metro:webservices-api-osgi:jar:2.3.1-b111 is missing, no dependency information available
Downloading: http://repo1.maven.org/maven2/org/glassfish/metro/webservices-api-osgi/2.3.1-b111/webservices-api-osgi-2.3.1-b111.jar



 Comments   
Comment by Romain Grécourt [ 03/Oct/13 ]

Can you share your mirroring configuration ?

There is no settings.xml requirement to build the GlassFish trunk.
The advised configuration is the only way to workaround the references to the maven.glassfish.org, and is only required to build 3.x workspaces.

Comment by Dave Whitla [ 10/Oct/13 ]

Hi Romain,

I apologise I've been unable to respond sooner.

<mirrors>
<mirror>
<id>maven-central</id>
<url>http://repo1.maven.org/maven2/</url>
<mirrorOf>*,!eclipselink.repository</mirrorOf>
</mirror>
</mirrors>

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

Ok, that's what I expected.
You can use the following, or no mirroring at all:

 <mirrors>
    <mirror>
      <id>maven-central</id>
      <url>http://repo1.maven.org/maven2/</url>
      <mirrorOf>*,!eclipselink.repository,!jvnet-nexus-promoted</mirrorOf>
    </mirror>
  </mirrors>

I've updated the documentation at https://wikis.oracle.com/display/GlassFish/FullBuildInstructions, this is the advised configuration for mirroring now, however note it's only required to build GlassFish 3.x

Please, try with or without the new mirroring and let me know if it's working, I will close this issue then.

Thanks.

Comment by Dave Whitla [ 20/Oct/13 ]

Thanks Romain,

Finally had time to progress my GFv4 stuff today.
By ignoring the old documentation the build does indeed complete successfully.

If I were being pedantic I'd resolve as a documentation error rather than invalid.





[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-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-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-19260] Java EE 7 RI Source Bundle Created: 30/Oct/12  Updated: 08/Aug/13  Resolved: 08/Aug/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b60
Fix Version/s: 4.0_b89_RC5

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

Issue Links:
Related
is related to GLASSFISH-19589 Java EE 7 RI Build binary Resolved

 Description   

The RI binaries delivered to licensees must be built from source to ensure consistency between the binaries and source, and as a result the source should be easily buildable by licensees so they can build the binaries themselves.

Detailed requirements for this are still being worked out and will be specified in the internal wiki page:

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Java+EE+7+RI+Source+Build



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 01/Nov/12 ]

Setting targeted fix to MS7 (hard code freeze) but initial RI build implementation will be made available by MS4 (b72).





[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-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-19861] In javax/faces/FactoryFinder.java, remove references to com.sun.faces.spi Created: 13/Mar/13  Updated: 11/Jun/13  Resolved: 11/Jun/13

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

Type: Task Priority: Trivial
Reporter: Ed Burns Assignee: Ed Burns
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: 16 hours
Time Spent: Not Specified
Original Estimate: 16 hours

Issue Links:
Dependency
depends on GLASSFISH-19841 JSF 2.2 dependencies not bundled in J... Closed

 Description   

javax.faces classes must not import com.sun.faces classes.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.4:compile (default-compile) on project javaee-web-api: Compilation failure: Compilation failure:
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[44,24] error: package com.sun.faces.spi does not exist
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[1076,8] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryManager
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[423,12] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryFinder
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[668,8] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryFinder
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[1037,12] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryManager
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[1040,37] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryManager
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[1077,12] error: cannot find symbol
[ERROR] symbol: class InjectionProvider
[ERROR] location: class FactoryManager
[ERROR] /scratch/ejburns/Documents/JavaEE/workareas/glassfish-1HEAD/appserver/javaee-api/javax.javaee-web-api/target/sources-dependency/javax/faces/FactoryFinder.java:[1077,40] error: cannot find symbol



 Comments   
Comment by Ed Burns [ 22/Mar/13 ]

I think this can be easily fixed by introducing a private static inner class inside the existing private static inner class FactoryManager that is a facade around com.sun.faces.spi.InjectionProvider and which uses reflection to get the job done.

Comment by Ed Burns [ 11/Jun/13 ]

After taking this issue to the JavaEE Architecture mailing list, I'm
closing this as invalid. Here is the relevant text from the email.

B> Edward Burns wrote on 05/28/13 15:28:

EB> Due to a decision made in 2004 there's plenty of executable code in
EB> the javax.faces API classes. For years we've had separate parts of
EB> the Mojarra source tree for the javax.faces API classes and the
EB> com.sun.faces impl classes.

EB> For those rare, yet unavoidable times when we need to share behavior
EB> between those two areas, we've resorted to a cheesy build-time
EB> template approach that basically puts the same class as a package
EB> private class in the places where we need it.

EB> The benefit of this approach is that there is no place where a
EB> javax.faces class imports a com.sun.faces class. (With one
EB> exception introduced in JSF 2.2)

EB> The drawback is that we have this silly copying.

EB> I would like to get a definitive ruling on whether or not we really
EB> need to maintain this separation. I hope we can simply drop it as
EB> long as we can continue produce a javax.faces-api.jar that is
EB> suitable for satisfying compile-time dependencies only, while the
EB> javax.faces.jar is the standalone implementation.

>>>>> On Wed, 29 May 2013 14:53:19 -0700, Bill Shannon said:

B> There's no universal requirement, no JCP requirement, no Oracle
B> requirement, and no Java EE requirement, to maintain such a
B> separation.

B> That said, if the customers of your API are expecting or demanding
B> such a separation, you should consider doing it. I said "should
B> consider", not "must do".

Therefore, I'm going to say that there is no prohibition on importing
com.sun.faces classes from classes in javax.faces packages.

We need to make the necessary changes to the build system to account for
this.

Ed





[GLASSFISH-20069] review API metadata Created: 26/Mar/13  Updated: 22/May/13  Resolved: 22/May/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b81
Fix Version/s: 4.0

Type: Task Priority: Blocker
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1 week
Time Spent: Not Specified
Original Estimate: 1 week

Issue Links:
Related
is related to GLASSFISH-19259 Java EE 7: javaee-api.jar Resolved

 Description   

Review API metadata. Review all API/Impl jars in order to verify that they comply with the rules described at https://wikis.oracle.com/display/GlassFish/Maven+Versioning+Rules



 Comments   
Comment by Joe Di Pol [ 22/May/13 ]

Romain implemented a maven plugin to check api metadata: spec-version-maven-plugin

This has been run on GF 4 and issues corrected.





[GLASSFISH-20455] Updated 3RD-PARTY-LICENSE.txt and 3RD-PARTY-LICENSE-WEB-PROFILE.txt Created: 02/May/13  Updated: 15/May/13  Resolved: 15/May/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b87_RC3
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Blocker
Reporter: Joe Di Pol Assignee: michael.y.chen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved

 Description   

We need updated content for 3RD-PARTY-LICENSE.txt and 3RD-PARTY-LICENSE-WEB-PROFILE.txt.



 Comments   
Comment by michael.y.chen [ 07/May/13 ]

3rd party license file update. This is a must have. txt file update with no risk.

Comment by michael.y.chen [ 09/May/13 ]

Nancy and I are working on this. We should have this done by 5/13.

Comment by michael.y.chen [ 14/May/13 ]

The 3rd party license files are delivered to RE. They will include it in the build.

Comment by Romain Grécourt [ 14/May/13 ]

3 party files are actually part of the source tree, see https://svn.java.net/svn/glassfish~svn/branches/4.0/appserver/packager/legal/src/main/resources/glassfish/legal/

Re-opening, the right way is to update those license files properly.

Comment by Snjezana Sevo-Zenzerovic [ 14/May/13 ]

Licenses checked into GlassFish trunk and branch workspaces (which is prerequisite for GF b89). Keeping the issue open until RI workspace checkin is complete.

Comment by Snjezana Sevo-Zenzerovic [ 15/May/13 ]

Updated 3rd party licenses checked into RI branch and trunk workspaces.





[GLASSFISH-20426] promoted artifact has wrong url Created: 29/Apr/13  Updated: 01/May/13  Resolved: 01/May/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b86_RC2
Fix Version/s: 4.0_b87_RC3

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

Tags: 4_0-approved

 Description   

org.glassfish.main/glassfish-parent/4.0-b84/glassfish-parent-4.0-b84.pom has following non-existent URL:

https://github.com/sonatype/jvnet-parent/glassfish-nucleus-parent/glassfish-parent/tags/4.0-b84/jvnet-parent/glassfish-nucleus-parent/glassfish-parent

This must be the case for other artifacts as well.



 Comments   
Comment by Romain Grécourt [ 29/Apr/13 ]
  • What is the impact on the customer of the bug?
    Maven pom showing irrelevant information

How likely is it that a customer will see the bug and how serious is the bug?
It's unprofesional, anybody looking at the pom could see the problem.

Is it a regression?
yes.
Does it meet other bug fix criteria (security, performance, etc.)?
no.
What CTS failures are caused by this bug?
None.

  • What is the cost/risk of fixing the bug?
    Trivial.

How risky is the fix? How much work is the fix? Is the fix complicated?
Trivial.

  • Is there an impact on documentation or message strings?
    no.
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    none.
  • Which is the targeted build of 4.0 for this fix?
    rc3.
  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.
    No.
Comment by Romain Grécourt [ 01/May/13 ]

Index: appserver/pom.xml
===================================================================
— appserver/pom.xml (revision 61761)
+++ appserver/pom.xml (working copy)
@@ -57,6 +57,7 @@
<scm>
<connection>scm:svn:https://svn.java.net/svn/glassfish~svn/trunk/main/appserver</connection>
<developerConnection>scm:svn:https://svn.java.net/svn/glassfish~svn/trunk/main/appserver</developerConnection>
+ <url>https://svn.java.net/svn/glassfish~svn/trunk/main/appserver</url>
</scm>

<properties>
Index: nucleus/pom.xml
===================================================================
— nucleus/pom.xml (revision 61761)
+++ nucleus/pom.xml (working copy)
@@ -59,6 +59,7 @@
<scm>
<connection>scm:svn:https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus</connection>
<developerConnection>scm:svn:https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus</developerConnection>
+ <url>https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus</url>
</scm>
<issueManagement>
<system>IssueTracker</system>
romano@dhcp-prague08-third-floor-10-163-25-212:~/workspaces/glassfish/git-ws/all/main$ svn commit -m "fix for GLASSFISH-20426"
Sending appserver/pom.xml
Sending nucleus/pom.xml
Transmitting file data ..
Committed revision 61762.





[GLASSFISH-20408] glassfish-verifier: bin script don't have execution permissions Created: 25/Apr/13  Updated: 01/May/13  Resolved: 01/May/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b86_RC2
Fix Version/s: 4.0_b87_RC3

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

Tags: 4_0-approved, packaging, updatecenter, updatetool, verifier

 Description   

glassfish-verifier: bin script don't have execution permissions



 Comments   
Comment by Romain Grécourt [ 25/Apr/13 ]
  • What is the impact on the customer of the bug?
    Direct impact if they try to install glassfish-verifier package, they will have to chmod the bin verify script.

How likely is it that a customer will see the bug and how serious is the bug?
Every person trying to install and use glassfish-verify will see the bug.
Not serious, but unprofessional

Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
Yes.

What CTS failures are caused by this bug?
None.

  • What is the cost/risk of fixing the bug?
    Easy, it should be a change in the pkg prototype to specify the permissions properly.

How risky is the fix? How much work is the fix? Is the fix complicated?
not risky.

  • Is there an impact on documentation or message strings?
    No.
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    Install glassfish-verifier and try to start the script after installation.
  • Which is the targeted build of 4.0 for this fix?
    b87
  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.
Comment by Romain Grécourt [ 01/May/13 ]

Project: glassfish
Repository: svn
Revision: 61763
Author: romain_grecourt
Date: 2013-05-01 09:33:41 UTC
Link:

Log Message:
------------
fix for GLASSFISH-20408, make glassfish-verifier bin scripts executable

Revisions:
----------
61763

Modified Paths:
---------------
trunk/main/appserver/packager/glassfish-verifier/pom.xml

Added Paths:
------------
trunk/main/appserver/packager/glassfish-verifier/src/main/assembly
trunk/main/appserver/packager/glassfish-verifier/src/main/assembly/glassfish-verifier.xml

Diffs:
------
Index: trunk/main/appserver/packager/glassfish-verifier/src/main/assembly/glassfish-verifier.xml
===================================================================
— trunk/main/appserver/packager/glassfish-verifier/src/main/assembly/glassfish-verifier.xml (revision 0)
+++ trunk/main/appserver/packager/glassfish-verifier/src/main/assembly/glassfish-verifier.xml (revision 61763)
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+
+ DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
+
+ Copyright (c) 2013 Oracle and/or its affiliates. All rights reserved.
+
+ The contents of this file are subject to the terms of either the GNU
+ General Public License Version 2 only ("GPL") or the Common Development
+ and Distribution License("CDDL") (collectively, the "License"). You
+ may not use this file except in compliance with the License. You can
+ obtain a copy of the License at
+ https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
+ or packager/legal/LICENSE.txt. See the License for the specific
+ language governing permissions and limitations under the License.
+
+ When distributing the software, include this License Header Notice in each
+ file and include the License file at packager/legal/LICENSE.txt.
+
+ GPL Classpath Exception:
+ Oracle designates this particular file as subject to the "Classpath"
+ exception as provided by Oracle in the GPL Version 2 section of the License
+ file that accompanied this code.
+
+ Modifications:
+ If applicable, add the following below the License Header, with the fields
+ enclosed by brackets [] replaced by your own identifying information:
+ "Portions Copyright [year] [name of copyright owner]"
+
+ Contributor(s):
+ If you wish your version of this file to be governed by only the CDDL or
+ only the GPL Version 2, indicate your decision by adding "[Contributor]
+ elects to include this software in this distribution under the [CDDL or GPL
+ Version 2] license." If you don't indicate a single choice of license, a
+ recipient has the option to distribute your version of this file under
+ either the CDDL, the GPL Version 2 or to extend the choice of license to
+ its licensees as provided above. However, if you add GPL Version 2 code
+ and therefore, elected the GPL Version 2 license, then the option applies
+ only if the new code is made subject to such option by the copyright
+ holder.
+
+-->
+
+<assembly xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
+
+ <id>stage-package</id>
+ <formats>
+ <format>dir</format>
+ </formats>
+
+ <includeBaseDirectory>false</includeBaseDirectory>
+ <fileSets>
+ <fileSet>
+ <directory>$

{temp.dir}/glassfish/bin</directory>
+ <outputDirectory>${install.dir.name}/glassfish/bin</outputDirectory>
+ <fileMode>755</fileMode>
+ </fileSet>
+ <fileSet>
+ <directory>${temp.dir}

</directory>
+ <excludes>
+ <exclude>glassfish/bin/*</exclude>
+ <exclude>pkg_proto.py</exclude>
+ </excludes>
+ <outputDirectory>$

{install.dir.name}

</outputDirectory>
+ </fileSet>
+ </fileSets>
+</assembly>

Property changes on: trunk/main/appserver/packager/glassfish-verifier/src/main/assembly/glassfish-verifier.xml
___________________________________________________________________
Added: svn:eol-style

    1. -0,0 +1 ##
      +native
      \ No newline at end of property
      Index: trunk/main/appserver/packager/glassfish-verifier/pom.xml
      ===================================================================
      • trunk/main/appserver/packager/glassfish-verifier/pom.xml (revision 61762)
        +++ trunk/main/appserver/packager/glassfish-verifier/pom.xml (revision 61763)
        @@ -52,6 +52,10 @@
        <name>Verifier Package</name>
        <packaging>distribution-fragment</packaging>
        <description>This pom describes how to assemble the Verifier package</description>
        +
        + <properties>
        + <temp.dir>$ {project.build.directory}

        /dependency</temp.dir>
        + </properties>

<build>
<plugins>





[GLASSFISH-20352] Integrate JDK 7u21 into Java EE 7 SDK cobundles Created: 19/Apr/13  Updated: 29/Apr/13  Resolved: 29/Apr/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b84_RC1
Fix Version/s: 4.0_b86_RC2

Type: Bug Priority: Major
Reporter: Snjezana Sevo-Zenzerovic Assignee: Snjezana Sevo-Zenzerovic
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved

 Description   

Java EE 7 SDK cobundles with JDK should contain JDK 7u21 which is about to be released.

  • What is the impact on the customer of the bug?

Java EE 7 SDK cobundles with JDK are expected to contain the latest available JDK release.

  • What is the cost/risk of fixing the bug?

Low risk.

  • Is there an impact on documentation or message strings?

Documentation should reference JDK 7u21 as part of SDK cobundles.

  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

BAT test suite, which is standard to verify JDK integrations.

  • Which is the targeted build of 4.0 for this fix?

SDK b85.

  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.

This integrates JDK 7u21.



 Comments   
Comment by Tom Mueller [ 19/Apr/13 ]

Approved for 4.0.





[GLASSFISH-20361] ml build missing localized woodstock jars Created: 19/Apr/13  Updated: 23/Apr/13  Resolved: 23/Apr/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b85
Fix Version/s: 4.0_b86_RC2

Type: Bug Priority: Major
Reporter: Anissa Lam Assignee: Snjezana Sevo-Zenzerovic
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved, console

 Description   

I believe the build team is aware of this, but want to keep track of this through the issue.

In latest nightly build, 4/18, there is still missing localized woodstock jars in the ml build.

In 3.1.2 release, the 2 jars is installed under glassfish/modules directory:
1. webui-jsf-plugin-l10n.jar
2. webui-jsf-suntheme-plugin-l10n.jar

Here is the workspace for the 2 woodstock jar for 3.1.2
https://svn.java.net/svn/glassfish~svn/branches/l10n-3.1.2/woodstock/



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 20/Apr/13 ]

These need to be moved from l10n workspace to GlassFish workspace and integrated into packager. Targeting b86.

Comment by Snjezana Sevo-Zenzerovic [ 23/Apr/13 ]
  • What is the impact on the customer of the bug?

Regression compared to 3.1.2 release. These two jars are required for full Admin GUI localization.

  • What is the cost/risk of fixing the bug?

Low risk. Fix is limited to migrating existing woodstock localized jar modules from l10n workspace to GlassFish workspace and adjusting pom files.

  • Is there an impact on documentation or message strings?

Fix migrates existing localized content to GF workspace, no further changes to message strings.

  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

Admin GUI l10n testing.

  • Which is the targeted build of 4.0 for this fix?

b86

  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.

N/A





[GLASSFISH-19881] Incorrect Product name Created: 15/Mar/13  Updated: 11/Apr/13  Due: 22/Mar/13  Resolved: 11/Apr/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b80_EE7MS6
Fix Version/s: 4.0_b85

Type: Bug Priority: Major
Reporter: jclingan Assignee: Snjezana Sevo-Zenzerovic
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

N/A


Tags: 4_0-approved

 Description   

/appserver/distributions/glassfish/target/dependency/glassfish4/glassfish/config/branding/glassfish-version.properties contains "BG Server" as the product name property. This appears in the browser when booting the admin console "Starting BG Server 4.0". This should be changed, likely to "GlassFish Server Open Source Edition" if this belongs to the open source branding module.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 02/Apr/13 ]

I think we'll need to add branding module which will override branding properties file to appserver workspace. I'll try to get this in by b83.

Comment by Snjezana Sevo-Zenzerovic [ 11/Apr/13 ]
  • What is the impact on the customer of the bug?

Regression compared to previous releases and significant branding issue.

  • What is the cost/risk of fixing the bug?

Low/moderate risk. Very limited impact on product runtime, but fix does span multiple components (need to create appserver specific branding fragment module with appropriate values and integrate that module into packager).

  • Is there an impact on documentation or message strings?

No.

  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

Admin GUI visual verification, possibly asadmin version subcommand regression testing.

  • Which is the targeted build of 4.0 for this fix?

b85

  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in? This might be list of
    Jira issues from that project or a list of revision messages.

N/A

Comment by Tom Mueller [ 11/Apr/13 ]

I'm not seeing this in my private builds. The content of the glassfish-version.properties file is:

product_name=GlassFish Server Open Source Edition
brief_product_name=GlassFish Server
abbrev_product_name=glassfish
major_version=4
minor_version=0
update_version=
build_id=tomuell-private
version_prefix=
version_suffix=
default_domain_template=appserver-domain.jar
admin_client_command_name=asadmin

The source file (appserver/packager/appserver-base/src/main/resources/config/branding/glassfish-version.properties) has:

product_name=$

{product.name}

brief_product_name=$

{brief_product_name}

abbrev_product_name=$

{abbrev_product_name}

major_version=$

{major_version}

minor_version=$

{minor_version}

update_version=$

{update_version}

build_id=$

{build.id}

version_prefix=$

{version_prefix}

version_suffix=$

{version_suffix}

default_domain_template=$

{default_domain_template}

admin_client_command_name=$

{admin_client_command_name}

Product name is set to GlassFish in the appserver/pom.xml file:

<product.name>GlassFish Server Open Source Edition</product.name>

Is this product name being overridden by the build system somewhere?

Comment by Tom Mueller [ 11/Apr/13 ]

A fix for this issue is approved for 4.0. However, it appears that more analysis is required to understand where the problem actually is.

Also, the distribution that actually has this should be identified (the description doesn't do this).

Comment by jclingan [ 11/Apr/13 ]

Tom, I pull this from svn directly:

svn checkout https://svn.java.net/svn/glassfish~svn/trunk/main

I wasn't sure if this was leaking into another build, and that makes it a P1. Regardless, BG Server shouldn't exist anywhere in the trunk, and that would be a P2.

Comment by Snjezana Sevo-Zenzerovic [ 11/Apr/13 ]

This turned out to be a red herring of a sort. So far we are unable to reproduce this with any of RE produced builds or with two developer build setups (Tom's and mine). So, closing as non-reproducible.





[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-20225] Integrate JDK 7u17 into Java EE 7 SDK cobundles Created: 08/Apr/13  Updated: 10/Apr/13  Resolved: 10/Apr/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b82_EE7MS7
Fix Version/s: 4.0_b83

Type: Bug Priority: Major
Reporter: Snjezana Sevo-Zenzerovic Assignee: Snjezana Sevo-Zenzerovic
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 4_0-approved

 Description   

Java EE 7 SDK build should produce cobundles with JDK 7 u17 (instead of current JDK 7u11)



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 08/Apr/13 ]
  • What is the impact on the customer of the bug?

Java EE 7 SDK cobundles with JDK should be based on the latest released JDK 7 version.

  • What is the cost/risk of fixing the bug?

Low/moderate risk.

  • Is there an impact on documentation or message strings?

Only SDK index pages affected since they reference bundled JDK version.

  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

QA usually verifies this type of change using automated BAT suite.

  • Which is the targeted build of 4.0 for this fix?

SDK b83

  • If this an integration of a new version of a component from another project,
    what are the changes that are being brought in?

This replaces JDK 7u11 with JDK7u17.

Comment by Tom Mueller [ 08/Apr/13 ]

Approved for 4.0





[GLASSFISH-19550] Build should stop using SNAPSHOT artifacts from remote repo by default Created: 17/Jan/13  Updated: 02/Apr/13  Resolved: 02/Apr/13

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

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


 Description   

To support partial workspace build, our POMs have been setup to use a SNAPSHOT repo by default. Since using SNAPSHOTs has other side effects, Romain and I have discussed a strategy to avoid using SNAPSHOTs by default. Those who want to do partial workspace build can use a separate profile which will have dependency on SNAPSHOT repo.

I have done some experiment which shows that maven does not fail the build in case a suitable SNAPSHOT parent does not exist in relativePath location. Look at the experiment below that I did after changing osgi-javaee-base/pom.xml to use a SNAPSHOT parent.

ss141213@Sahoo:/space/ss141213/WS/ff/trunk/module$ rm -rf ~/.m2/repository/org/glassfish/fighterfish/module.parent-pom/

ss141213@Sahoo:/space/ss141213/WS/ff/trunk/module$ mvn -f osgi-javaee-base/pom.xml clean
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.glassfish.fighterfish:osgi-javaee-base:1.0.6-SNAPSHOT (/space/ss141213/WS/ff/trunk/module/osgi-javaee-base/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact org.glassfish.fighterfish:module.parent-pom:pom:1.0.6-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 46, column 13 -> [Help 2]

ss141213@Sahoo:/space/ss141213/WS/ff/trunk/module$ mvn -f parent-pom/pom.xml install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.glassfish.fighterfish:module.parent-pom:pom:1.0.6-SNAPSHOT
[WARNING] 'parent.relativePath' points at org.glassfish.fighterfish:module-build-aggregator instead of net.java:jvnet-parent, please verify your project structure @ line 36, column 10
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Parent POM for all FighterFish Modules 1.0.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — maven-enforcer-plugin:1.0:enforce (enforce-maven) @ module.parent-pom —
[INFO]
[INFO] — maven-bundle-plugin:2.0.1:manifest (bundle-manifest) @ module.parent-pom —
[WARNING] Ignoring project type pom - supportedProjectTypes = [hk2-jar, bundle, jar]
[INFO]
[INFO] — maven-install-plugin:2.3.1:install (default-install) @ module.parent-pom —
[INFO] Installing /space/ss141213/WS/ff/trunk/module/parent-pom/pom.xml to /home/ss141213/.m2/repository/org/glassfish/fighterfish/module.parent-pom/1.0.6-SNAPSHOT/module.parent-pom-1.0.6-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

ss141213@Sahoo:/space/ss141213/WS/ff/trunk/module$ mvn -f osgi-javaee-base/pom.xml clean
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.glassfish.fighterfish:osgi-javaee-base:jar:1.0.6-SNAPSHOT
[WARNING] 'parent.relativePath' points at org.glassfish.fighterfish:module-build-aggregator instead of org.glassfish.fighterfish:module.parent-pom, please verify your project structure @ line 46, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Base module for providing support for OSGi in Java EE applications 1.0.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — maven-clean-plugin:2.4.1:clean (default-clean) @ osgi-javaee-base —
[INFO] Deleting /space/ss141213/WS/ff/trunk/module/osgi-javaee-base/target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

What this tells me is that if we don't have SNAPSHOT repo, then build will still not require a specific layout. This is contary to what you had assumed.



 Comments   
Comment by Romain Grécourt [ 07/Feb/13 ]

Since the java.net snapshot repo is defined in jvnet-parent, we will need to push a new release of it.
I suggest we isolate the snapshot and staging repositories into separate profiles "snapshot" and "staging".

I believe we can make "promoted" configured by default. jvnet release repository does not make sense to us since it's synched in maven central.

Eventually, one would use snapshot as follow:

> mvn install -Psnapshot
Comment by Romain Grécourt [ 02/Apr/13 ]

fixed with jvnet-parent:4





[GLASSFISH-19844] main-docs-l10n: need help to set up to publish Glassfish 4.0 L10n docs to MVN Repository Created: 12/Mar/13  Updated: 28/Mar/13  Due: 13/Mar/13  Resolved: 28/Mar/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b79
Fix Version/s: 4.0_b82_EE7MS7

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

UA (docs) l10n workspace (https://svn.java.net/svn/glassfish~svn/trunk/main-docs-l10n)


Issue Links:
Dependency
blocks GLASSFISH-18266 Unlocalized strings in the output of ... Reopened
Tags: build

 Description   

I am planning to follow the English doc process of Glassfish 4.0 for l10n docs. In order to do this, I was told that we need to:

1. set up a Hudson job similar to gf-trunk-docs-promotion, i.e. gf-trunk-docs-l10n
2. modify pom.xml under main/nucleus, so that it'll build something like $

{v3-docs.version}

for l10n docs
3. modify pom.xml under main, so that the l10n docs become part of the build

Could you shed some light on how to go about doing these? I have 2 test l10n docs checked into main-docs-l10n to do a test publish once we have the set up ready.



 Comments   
Comment by clyang [ 19/Mar/13 ]

The translated doc has come back.
I am processing the docs to get them ready to check into main-docs-l10n workspace.
Do you have an ETA on when this will be done?

Thanks, Claire

Comment by Romain Grécourt [ 25/Mar/13 ]

work stopped because of java.net issues.

Comment by clyang [ 28/Mar/13 ]

Hi Romain,

I see that there is a successful build on gf-trunk-docs-l10n-promotion. Thanks.

Here's a list of things that I think is needed:

1. I need permission to start a new build on hudson (a "build" link) so that I can start a new build once l10n stuff is checked in.
2. I need something similar to "<v3-docs.version>4.0-b21</v3-docs.version>" in main/nucleus/pom.xml where I can specify the l10n-docs build. Perhaps "v3-docs-l10n" just to be consistent with the docs. (Though it's really "v4" instead of "v3".)

Thanks, Claire

Comment by Romain Grécourt [ 28/Mar/13 ]

I just gave you the permission. Will do the pom changes at review time.

Comment by clyang [ 28/Mar/13 ]

I'm getting an error from "Build Now":

java -version
/tmp/hudson154610603941677584.sh: line 14: /net/bat-sca.us.oracle.com/repine/export2/hudson/tools/solaris-sparcv9/java1.6.0_22/bin/java: cannot execute binary file

Comment by Romain Grécourt [ 28/Mar/13 ]

fixed.





[GLASSFISH-20024] Class-Path property in javaee.jar MANIFEST does not reference javax.batch.api (javax.batch-api.jar) package Created: 25/Mar/13  Updated: 25/Mar/13  Resolved: 25/Mar/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b82_EE7MS7
Fix Version/s: 4.0_b82_EE7MS7

Type: Bug Priority: Minor
Reporter: Ryan O'Connell Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The Class-Path property defined in the javaee.jar's MANIFEST does not include a reference to the new batch APIs. Specifically, the package javax.batch.api. Adding a reference to javax.batch-api.jar may fix the issue. I was looking at the March 24th nightly of GF v4.



 Comments   
Comment by Ryan O'Connell [ 25/Mar/13 ]

change packaging -> batch and update build ID since it was build 82.

Comment by Romain Grécourt [ 25/Mar/13 ]

Committed revision 60771.





[GLASSFISH-19982] [regression] GlassFish 4-b80-ml.zip generates bundle warnings flooding the server.log Created: 21/Mar/13  Updated: 21/Mar/13  Resolved: 21/Mar/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b80_EE7MS6
Fix Version/s: 4.0_b81

Type: Bug Priority: Blocker
Reporter: myfear Assignee: Joe Di Pol
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Welcome to GlassFish Server Open Source Edition 4.0 (build 80)
JDK 1.7_u15
Win 7-64bit


Tags: fishcat

 Description   

Starting GF I get a bunch of warnings for every module all following this example:

[2013-03-21T07:22:48.062+0100] [glassfish 4.0] [WARNING] [] [org.jvnet.hk2.osgiadapter] [tid: _ThreadID=119 _ThreadName=admin-listener(6)] [timeMillis: 1363846968062] [levelValue: 900] [[
Exception org.osgi.framework.BundleException: Could not create bundle object. while adding location = file:/D:/glassfish4-b80-ml/glassfish/modules/appclient-server-core-l10n.jar]]

This is flooding the logfile :<



 Comments   
Comment by TangYong [ 21/Mar/13 ]

In windows xp, the issue does not happen. as for win 7 64 bit, I will validate it from my home env.

Comment by myfear [ 21/Mar/13 ]

I could provide a complete logfile ... drop me a line myfear at web dot de

Comment by Sanjeeb Sahoo [ 21/Mar/13 ]

While using 4.0-b80-ml.zip on Linux, I do see exceptions like:

[#|2013-03-21T01:01:09.317-0700|WARNING|glassfish 4.0|org.jvnet.hk2.osgiadapter|_ThreadID=78;_ThreadName=Thread-12;_TimeMillis=1363852869317;_LevelValue=900;|
Exception org.osgi.framework.BundleException: Could not create bundle object. while adding location = file:/scratch/sanjsaho/software/gf-4.0-b80-ml/glassfish4/glassfish/modules/console-corba-plugin-l10n.jar|#]

But, I also notice exceptions at the start of the server like this:

Launching GlassFish on Felix platform
Mar 21, 2013 1:00:59 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner createBundleProvisioner
INFO: Create bundle provisioner class = class com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.
Mar 21, 2013 1:00:59 AM com.sun.enterprise.glassfish.bootstrap.LogFacade log
WARNING: Failed to install file:/scratch/sanjsaho/software/gf-4.0-b80-ml/glassfish4/glassfish/modules/console-jms-plugin-l10n.jar.
org.osgi.framework.BundleException: Could not create bundle object.
at org.apache.felix.framework.Felix.installBundle(Felix.java:2940)
at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
at com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.install(BundleProvisioner.java:445)
at com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.installBundles(BundleProvisioner.java:205)
at com.sun.enterprise.glassfish.bootstrap.osgi.OSGiGlassFishRuntimeBuilder.build(OSGiGlassFishRuntimeBuilder.java:142)
at org.glassfish.embeddable.GlassFishRuntime._bootstrap(GlassFishRuntime.java:157)
at org.glassfish.embeddable.GlassFishRuntime.bootstrap(GlassFishRuntime.java:110)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:112)
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 com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:97)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:54)
Caused by: java.lang.IllegalArgumentException: invalid version "$

Unknown macro: {project.osgi.version}

": non-numeric "${project"
at org.osgi.framework.Version.parseInt(Version.java:170)
at org.osgi.framework.Version.<init>(Version.java:126)
at org.apache.felix.framework.util.VersionRange.parse(VersionRange.java:98)
at org.apache.felix.framework.util.manifestparser.ManifestParser.parseFragmentHost(ManifestParser.java:1335)
at org.apache.felix.framework.util.manifestparser.ManifestParser.<init>(ManifestParser.java:146)
at org.apache.felix.framework.BundleRevisionImpl.<init>(BundleRevisionImpl.java:118)
at org.apache.felix.framework.BundleImpl.createRevision(BundleImpl.java:1199)
at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:96)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2887)
... 13 more
Caused by: java.lang.NumberFormatException: For input string: "${project"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:481)
at java.lang.Integer.parseInt(Integer.java:527)
at org.osgi.framework.Version.parseInt(Version.java:168)
... 21 more

To see them, you need to start with -v option:

asadmin start-domain -v

This exception is happening because of bad manifest:

[MANIFEST console-jms-plugin-l10n.jar]
Archiver-Version Plexus Archiver
Bnd-LastModified 1363208767995
Build-Jdk 1.7.0_09
Built-By java_re
Bundle-Description Java.net - The Source for Java Technology Collaboration
Bundle-ManifestVersion 2
Bundle-Name Admin Console JMS Plugin l10n
Bundle-SymbolicName org.glassfish.main.admingui.console-jms-plugin-l10n
Bundle-Version 4.0.0.b80
Created-By Apache Maven Bundle Plugin
Fragment-Host org.glassfish.main.admingui.console-jms-plugin; bundle-version=${project.osgi.version}
Manifest-Version 1.0
Tool Bnd-1.15.0

The good thing is I don't see such exceptions in b81. In b81, the manifest has been fixed. I don't know how we ended up promoting b80 with such a blocking bug, but that's a question for our release engineering team. I am assigning it to them. They should close it as RESOLVED with an explanation for the svn revision that fixed the issue. They should also fix promotion process to avoid such issues in future.

Comment by Romain Grécourt [ 21/Mar/13 ]

You don't know ? The answer is easy though.

I fixed this last sunday, b81 includes the fix.

Comment by Sanjeeb Sahoo [ 21/Mar/13 ]

I don't deny the answer was perhaps easy to find by looking at all check in logs. I didn't put that effort. I am still looking for an answer as to how how we promoted this zip? Don't we run any tests again ml builds?

Comment by Romain Grécourt [ 21/Mar/13 ]

My comment was exactly about this question.
Note that those are warinings, even if we tested the ml bundles, the tests would have passed.

Comment by Romain Grécourt [ 21/Mar/13 ]

There is no test that uses l10n bundles AFAIK.

Comment by Sanjeeb Sahoo [ 21/Mar/13 ]

Thanks for clarifying, Romain. You are absolutely right, they are warnings. I missed that part. Server does come up fine. It's just that the l10n does not work. So, that does reduce the severity of the issue to major from blocking. I assume our l10n QA would have caught that issue in due course of time.





[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-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-19783] common/simple-glassfish-api module has groupid org.glassfish.main rather than org.glassfish.main.common Created: 06/Mar/13  Updated: 07/Mar/13  Resolved: 07/Mar/13

Status: Closed
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b78
Fix Version/s: 4.0_b80_EE7MS6

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


 Description   

The nucleus/common/simple-glassfish-api/pom.xml has the following for the parent:

<parent>
<groupId>org.glassfish.main</groupId>
<artifactId>glassfish-nucleus-parent</artifactId>
<version>4.0-SNAPSHOT</version>
<relativePath>../../pom.xml</relativePath>
</parent>

This means that it's group id is org.glassfish.main rather than org.glassfish.main.common.

Like other modules under common, the parent should be common/pom.xml (../pom.xml).






[GLASSFISH-19589] Java EE 7 RI Build binary Created: 25/Jan/13  Updated: 05/Mar/13  Resolved: 05/Mar/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b68_EE7MS3
Fix Version/s: 4.0_b78

Type: New Feature Priority: Critical
Reporter: Joe Di Pol Assignee: Snjezana Sevo-Zenzerovic
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-19260 Java EE 7 RI Source Bundle Resolved

 Description   

We need to produce a binary RI build for Java EE 7.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 15/Feb/13 ]

Initial set of RI binaries has been produced. Targeting b78 for full integration with GlassFish 4.0 promoted builds and closure on this.

Comment by Snjezana Sevo-Zenzerovic [ 05/Mar/13 ]

Marking as fixed. RI builds are available, incremental improvements will be tracked separately.





[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-19765] Zip distribution produced by continuous builds have files with future time stamp Created: 02/Mar/13  Updated: 05/Mar/13  Resolved: 05/Mar/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b78
Fix Version/s: 4.0_b79

Type: Bug Priority: Blocker
Reporter: Sanjeeb Sahoo Assignee: Jill Sato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Status Whiteboard:

Workaround:
On Linux you can fix the timestamps like this:
unzip -DD glassfish.zip
On systems where -DD is not an option, use touch:
find glassfish4 -exec touch {}\;


 Description   

I have been trying to understand why fighterfish job started to fail in unexpected way and what I have found is that one of the build machine's clock may not correctly set or there is something wrong with build. I just picked glassfish.zip from build #13576 [1] that was done in sc11152330.us.oracle.com at 5.30AM on March 1.

http://gf-hudson.us.oracle.com/hudson/job/gf-trunk-build-continuous/13576/artifact/bundles/glassfish.zip
unzip glassfish.zip

unzip -l glassfish.zip | grep glassfish.jar
127784 03-01-2013 13:55 glassfish4/glassfish/modules/glassfish.jar

stat glassfish4/glassfish/modules/glassfish.jar
File: `glassfish4/glassfish/modules/glassfish.jar'
Size: 127784 Blocks: 256 IO Block: 4096 regular file
Device: ca02h/51714d Inode: 1324425 Links: 1
Access: (0644/rw-rr-) Uid: (142213/sanjsaho) Gid: ( 10/ wheel)
Access: 2013-03-01 13:55:58.000000000 -0800
Modify: 2013-03-01 13:55:58.000000000 -0800
Change: 2013-03-01 09:34:57.886099896 -0800

Do you notice the file has a last modified timestamp of March 01@13:55:58 PST?

Because this file has a timestamp in future, it is considered newer than some other files and that in turn causes my tests to fail. Is it a clock issue or some other build issue? What I also don't understand why the last change timestamp is different from the other timestamps by such a huge margin.

Thanks,
Sahoo

[1] http://gf-hudson.us.oracle.com/hudson/job/gf-trunk-build-continuous/13576/



 Comments   
Comment by Tom Mueller [ 04/Mar/13 ]

This problem might be effecting the developer scenario performance benchmarks. See:
http://hudson-sca.us.oracle.com/job/as-dev-benchmark-trunk-win/japex/ (internal link)

When the test is run within hours of when the glassfish.zip was produced, then we get really long server startup times. When the test is run later with the same file, then the startup time is fine.

Comment by Jill Sato [ 04/Mar/13 ]

The gf-trunk-build-continuous job recently was moved over to use the Oracle VM machines (POOL-1 machines).
All the Oracle VMs set up by GIT have timezone TZ=UTC.
Looks like the ant zip classes use the UTC timestamp to zip the classes (8 hrs ahead of Pacific Time).
That's why the files look like they are "in the future."

% cat /etc/default/init
TZ=UTC
CMASK=022
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1

And this symlink exists:
/etc/TIMEZONE -> /etc/default/init

However, TZ in my environment is set to PST8PDT when I'm on those VMs.
% env | grep TZ
TZ=PST8PDT

and the 'date' command still says PST on that same machine.
% date
Monday, March 4, 2013 09:48:44 AM PST

Comment by Jill Sato [ 04/Mar/13 ]

ok, changed TZ value in /etc/default/init and doing another build on gf-trunk-build-continuous.
Will see if that fixes it...

TZ=US/Pacific

Comment by Tom Mueller [ 04/Mar/13 ]

While the Felix optimizations can certainly depend on the system time being later than the timestamp of every file, it seems that it should be able to deal with future timestamps in a graceful way. The server should not hang or crash just because there is a future timestamp.

After the build problem is fixed, it seems that there should still be new issue filed for Felix (or whereever this problem is) that addresses the stability issue.

Comment by Jill Sato [ 05/Mar/13 ]

I changed the timezones on all machines in POOL-1 to be US/Pacific and now the zip distributions match the time of the system starting with gf-trunk-build-continuous #13598.
Please confirm if this fixes your tests.

Comment by Jill Sato [ 05/Mar/13 ]

Setting timezone to Pacific on all systems solves the problem. Thanks.

TZ=US/Pacific

Comment by Tom Mueller [ 05/Mar/13 ]

Seems to have fixed the developer scenario benchmark.





[GLASSFISH-19655] provide javax.javaee-endorsed-api:7.x Created: 08/Feb/13  Updated: 26/Feb/13  Resolved: 26/Feb/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b73, 4.0_b74
Fix Version/s: 4.0_b78

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

Issue Links:
Dependency
depends on GLASSFISH-19259 Java EE 7: javaee-api.jar Resolved

 Description   

Provide an endorse-api jar for EE7
See http://search.maven.org/remotecontent?filepath=javax/javaee-endorsed-api/6.0/javaee-endorsed-api-6.0.jar






[GLASSFISH-19682] asadmin -v display extra characters Created: 15/Feb/13  Updated: 21/Feb/13  Resolved: 21/Feb/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b76_EE7MS5
Fix Version/s: 4.0_b77

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

OEL6


Issue Links:
Related
is related to GLASSFISH-19708 version popup displays GlassFish Serv... Resolved
Status Whiteboard:

Request issue be resolved in GF 4.0 release.


 Description   

Build :GlassFish Server Open Source Edition 4.0 B76

Steps to reproduce :

1) Install GF4.0 B76
2) Check for asadmin version -v
Its will display the extra characters "$

{version_suffix}" on the console.

# ./asadmin version -v
Version = GlassFish Server Open Source Edition 4.0 ${version_suffix}

(build 76), JRE version 1.7.0-internal
Command version executed successfully.

You can also see this issue on Admin console.
Login to admin console and click on version tab , you can see the issue.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 15/Feb/13 ]

Moving to appropriate subcomponent for evaluation.

Comment by Tom Mueller [ 15/Feb/13 ]

This problem is seen in the promoted builds. For example:
http://javaweb.us.oracle.com/java/re/glassfish/4.0/promoted/b76/archive/bundles/glassfish-4.0-b76.zip

The problem is in the glassfish/config/branding/glassfish-version.properties file where the version_suffix property is not being substituted at build time:

version_suffix=$

{version_suffix}

This problem does not happen on the continuous builds.

The way this is supposed to work is that the packager/appserver-base package does a filtering substitution on the resources, including the glassfish-version.properties file. The version_suffix property is defined in the appserver/pom.xml file.

For the official build, this value is not being set properly.

Comment by Romain Grécourt [ 21/Feb/13 ]
romano@dhcp-prague08-third-floor-10-163-25-212:~/Downloads/glassfish4/glassfish$ bin/asadmin version
Version string could not be obtained from Server [localhost:4848].
(Turn debugging on e.g. by setting AS_DEBUG=true in your environment, to see the details.)
Using locally retrieved version string from version class.
Version = GlassFish Server Open Source Edition  4.0  (build 77)
Command version executed successfully.

romano@dhcp-prague08-third-floor-10-163-25-212:~/Downloads/glassfish4/glassfish$ bin/asadmin start-domain
Waiting for domain1 to start .......
Successfully started the domain : domain1
domain  Location: /Users/romano/Downloads/glassfish4/glassfish/domains/domain1
Log File: /Users/romano/Downloads/glassfish4/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

romano@dhcp-prague08-third-floor-10-163-25-212:~/Downloads/glassfish4/glassfish$ bin/asadmin version
Version = GlassFish Server Open Source Edition  4.0  (build 77)
Command version executed successfully.




[GLASSFISH-19620] JPA 2.1 JARs missing from javaee-api Created: 02/Feb/13  Updated: 13/Feb/13  Resolved: 13/Feb/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b73, 4.0_b74
Fix Version/s: 4.0_b75

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

Issue Links:
Related
is related to GLASSFISH-19377 use javax.persistence-api v2.x for EE... Resolved

 Description   

JPA 2.1 jars are available at:

<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>org.eclipse.persistence.jpa</artifactId>
<version>2.5.0-M6</version>
<scope>provided</scope>
</dependency>

and already integrated in GlassFish 4. JAR published for b72 does not have the correct version of JPA APIs, specifically CriteriaBuilder.createCriteraiaDelete and createCriteriaUpdate are missing.



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

2.5.0-M7 has been integrated yersterday. I was not able to consume eclipselink's artifact before due to an encoding issue in the source bundle.
I need to verify that, if working it will be included in b75





[GLASSFISH-13949] Wrong checksum on maven repository Created: 13/Oct/10  Updated: 22/Jan/13  Resolved: 22/Jan/13

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

Type: Bug Priority: Major
Reporter: fabriciolemos Assignee: Romain Grécourt
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,949
Tags: 3_1-exclude

 Description   

Some POMs are with the wrong checksum on Glassfish Maven Repository, which
causes artifactory to reject those POMs if validation is enabled.

The files I´m having problems are:
http://download.java.net/maven/glassfish/org/jboss/weld/weld-core-bom/1.0.1-
Final/weld-core-bom-1.0.1-Final.pom
and
http://download.java.net/maven/glassfish/org/jboss/weld/weld-api-bom/1.0-
SP1/weld-api-bom-1.0-SP1.pom

Don´t know if other files have the same problem.

This issue was previously reported at Jboss issue tracking: Some POMs are with
the wrong checksum on Glassfish Maven Repository, which causes artifactory to
reject those POMs if validation is enabled.

The files I´m having problems are:
http://download.java.net/maven/glassfish/org/jboss/weld/weld-core-bom/1.0.1-
Final/weld-core-bom-1.0.1-Final.pom
and
http://download.java.net/maven/glassfish/org/jboss/weld/weld-api-bom/1.0-
SP1/weld-api-bom-1.0-SP1.pom

Don´t know if other files have the same problem.

This issue was previously reported at Jboss issue tracking:
https://jira.jboss.org/browse/JBBUILD-655



 Comments   
Comment by Sivakumar Thyagarajan [ 14/Oct/10 ]

reassigning issue to Jane and the build_system subcomponent

Comment by janey [ 15/Oct/10 ]

The artifacts org.jboss.weld:weld-core-bom:1.0.1-Final and org.jboss.weld:weld-api-bom:1.0-SP1
are published to the GlassFish Maven repository because we are doing source-build for external
projects that are referenced in GlassFish v3. The original thought was that GlassFish is the only
recipient of the source-build artifacts. Since Glassfish Maven repository is open to the community,
other project can reference it.

These artifacts should actually be published to the JBoss Maven repository. I've asked Siva to see if
this artifact can be published to the JBoss Maven repository and I'll remove the Weld artifacts in the
GlassFish Maven repository.

Another possible fix is to redeploy the MD5 files... but ultimately, this artifact should actually be
coming from JBoss repo.

Comment by pgier [ 15/Oct/10 ]

The Weld project now deploys their releases directly to the Maven central repo
(repo1.maven.org) so a lot of these artifacts are not in our repository. The
Glassfish repo was taking higher priority than Maven central in some of our
builds, so that's why we ended up seeing the bad checksums.

Comment by janey [ 19/Oct/10 ]

The reason why the Weld artifacts are deployed with bad checksum is because of this bug:
http://jira.codehaus.org/browse/MNG-4301

We are using Maven 2.2.1 to build and deploy the artifact. Will need to add the following extension in
the pom.xml:

<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>

Comment by Romain Grécourt [ 22/Jan/13 ]

Won't fix as GlassFish is now using maven-3 and deployment is done to maven central.
Note that download.java.net/maven2 is not supported anymore.





[GLASSFISH-13870] some directories are not ignored properly Created: 07/Oct/10  Updated: 22/Jan/13  Resolved: 22/Jan/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 3.1
Fix Version/s: 4.0_b64_EE7MS2

Type: Bug Priority: Minor
Reporter: vince kraemer Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,870

 Description   

I noticed that if I do 'svn diff' after 'mvn install' some 'target' directories appear in the this of changed files.
see this patch for an example:
https://glassfish.dev.java.net/nonav/issues/showattachment.cgi/5094/13277.diff

It isn't a big deal. It is just a 'usability thing'.



 Comments   
Comment by Tom Mueller [ 24/Dec/12 ]

The current list includes these files:

$ svn status
? appserver/appclient/client/acc-standalone-l10n/target
? appserver/appclient/client/acc-l10n/target
? appserver/tests/hk2/isolation/web/iso1/target
? appserver/tests/hk2/isolation/web/iso2/target
? appserver/common/stats77-l10n/target

Assigning this to the build_system component to have these files fixed. The RE team sets the ignore flag regularly for new modules that are created, but these must have been missed.

Comment by Romain Grécourt [ 22/Jan/13 ]

the reported unversionned directory are ignored.





[GLASSFISH-13982] javax.inject in glassfish repo does not match Maven central repo Created: 14/Oct/10  Updated: 22/Jan/13  Resolved: 22/Jan/13

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

Type: Bug Priority: Major
Reporter: pgier Assignee: Romain Grécourt
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 13,982
Tags: 3_1-exclude

 Description   

The javax.inject version 1 jar in the glassfish repository [1] does not match
the same jar in the central Maven repository [2]. The class files in the
glassfish jar are compiled for Java 6 and the class files in the central jar are
compiled for Java 5. Artifacts that have the same GAV (groupId, artifactId, and
version) in a Maven repository should have exactly the same content. Otherwise
you can run into conflicts in the local Maven repository. For example, someone
expecting to download the artifact from central could add the glassfish
repository for some unrelated artifacts and end up with the incorrect file.

[1]http://download.java.net/maven/glassfish/javax/inject/javax.inject/1/
[2]http://repo2.maven.org/maven2/javax/inject/javax.inject/1/



 Comments   
Comment by Sivakumar Thyagarajan [ 14/Oct/10 ]

Adding myself to the interest list

Comment by janey [ 15/Oct/10 ]

The artifacts javax.inject:1 is published to the GlassFish Maven repository because we are doing
source-build for external projects that are referenced in GlassFish v3. The original thought was that
GlassFish is the only recipient of the source-build artifacts. Since Glassfish Maven repository is open
to the community, other project can reference it.

To fix this inconsistency with the central Maven repo, I will remove javax.inject from GlassFish repo.

Comment by pgier [ 15/Oct/10 ]

Just FYI, we've had this same issue come up in the JBoss repository since we
also sometimes rebuild dependency jars. The solution that we came up with is to
give an extra version qualifier to any jars that have been rebuilt. So the
original jar in central might be version 1.0, but our rebuilt jar in the JBoss
repository is version 1.0-jboss-1. This way the GAV is still unique, but it's
clear that these jars are related.

Comment by janey [ 18/Oct/10 ]

Thanks for the suggestion. Our source build requirement is that we don't make any customization to the
build script and source code.

I spoke to Sahoo and we discussed that we will deploy the 3rd party artifacts to our internal Nexus server.
The GlassFish Hudson job will reference the internal Nexus Server. The community GF build should not be
impacted by this change.

Thanks,
Jane

Comment by Romain Grécourt [ 22/Jan/13 ]

download.java.net is not a supported maven repository anymore. See maven central and maven.java.net





Java EE 7: javaee-api.jar (GLASSFISH-19259)

[GLASSFISH-19375] provide javax.ejb-api under official coordinates Created: 27/Nov/12  Updated: 22/Jan/13  Due: 03/Dec/13  Resolved: 22/Jan/13

Status: Closed
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b63
Fix Version/s: 4.0_b65

Type: Sub-task Priority: Major
Reporter: Romain Grécourt Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1 week
Time Spent: Not Specified
Original Estimate: 1 week
Environment:

any


Tags: ejb, glassfish, maven

 Description   

1) copy those sources to
> https://svn.java.net/svn/glassfish~svn/trunk/api/javaee-api/javax.ejb
whithout javax.interceptor as it will be released apart.

2) setup release.sh scripts for releasing new versions easily
3) remove appserver/ejb/javax.ejb and replace all the occurences of org.glassfish.main:javax.ejb by javax.ejb:javax.ejb-api or javax.interceptor:javax.interceptor-api

Official coordinates will be javax.ejb:javax-ejb-api:3.2

see https://wikis.oracle.com/display/GlassFish/Maven+Versioning+Rules






[GLASSFISH-19467] Publish javaee7-api.jar in Maven Created: 17/Dec/12  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: 4.0_b73

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


 Description   

Publish javaee7-api.jar in Maven



 Comments   
Comment by Romain Grécourt [ 18/Jan/13 ]

See:





[GLASSFISH-17546] cannot build glassfish 3.1.1 from sources (tag 3.1.1), DependencyResolutionException, Could not resolve dependency Created: 01/Nov/11  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Blocker
Reporter: Veit Ullmann Assignee: Unassigned
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows 7, 64 bit


Tags: 3_1_2-exclude, build, ejb, glassfish-3-1-1, repository

 Description   

downloaded sources from https://svn.java.net/svn/glassfish~svn/tags/3.1.1
called : mvn install
got the following exception:

[INFO] EJB Timer Service Application ..................... SUCCESS [0.203s]
[INFO] GlassFish EJB timer app database init scripts ..... SUCCESS [0.172s]
[INFO] EJB tier for GlassFish ............................ FAILURE [0.047s]

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:31.576s
[INFO] Finished at: Tue Nov 01 09:20:14 CET 2011
[INFO] Final Memory: 155M/432M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ejb-all: Could not resolve dependencies for project org.glassfish.ejb:ejb-all:pom:3.1.1: Could not find artifact org.glassfish.ejb:ejb-timer-databases:distribution-fragment:3.1.1 in glassfish-repo-archive (http://maven.glassfish.org/content/groups/glassfish) -> [Help 1]
[ERROR]



 Comments   
Comment by Veit Ullmann [ 01/Nov/11 ]

is this the reason?

[INFO] — maven-bundle-plugin:2.0.1:manifest (bundle-manifest) @ ejb-timer-databases —
[WARNING] Ignoring project type distribution-fragment - supportedProjectTypes = [hk2-jar, bundle]
[INFO]

Comment by Veit Ullmann [ 02/Nov/11 ]

I used maven 3.0.3 when the error happened, after using maven 2.1.1 it was successful.

Comment by scatari [ 02/Nov/11 ]

This is a maven issue: Please see http://jira.codehaus.org/browse/MNG-5135
3.1.2 will not use maven 3.0.3, targeting this bug for 4.0.





[GLASSFISH-17545] cannot build glassfish 3.1.1 from sources (tag 3.1.1) Created: 01/Nov/11  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Blocker
Reporter: Veit Ullmann Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows 7, 64 bit


Tags: 3_1_2-exclude, build, cmp, persistence

 Description   

downloaded sources from https://svn.java.net/svn/glassfish~svn/tags/3.1.1
called : mvn install
got the following exception:

[INFO] antlr.all version 2.7.6 repackaged as a module .... SUCCESS [0.727s]
[INFO] support-sqlstore module for cmp ................... SUCCESS [11.676s]
[INFO] support ejb module for cmp ........................ SUCCESS [8.311s]
[INFO] GlassFish cmp scripts ............................. SUCCESS [0.058s]
[INFO] CMP tier for GlassFish ............................ FAILURE [3.756s]
[INFO] GlassFish Extras modules .......................... SKIPPED
[INFO] GlassFish Grizzly adapter container implementation SKIPPED
[INFO] GlassFish OSGi adapter to use OSGi modules as application code SKIPPED

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:21.542s
[INFO] Finished at: Tue Nov 01 08:54:54 CET 2011
[INFO] Final Memory: 172M/1922M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cmp-all: Could not resolve dependencies for project org.glassfish.persistence.cmp:cmp-all:pom:3.1.1: Could not find artifact org.glassfish.persistence.cmp:cmp-scripts:distribution-fragment:3.1.1 in glassfish-repo-archive (http://maven.glassfish.org/content/groups/glassfish)



 Comments   
Comment by Veit Ullmann [ 01/Nov/11 ]

[INFO] — maven-bundle-plugin:2.0.1:manifest (bundle-manifest) @ ejb-timer-databases —
[WARNING] Ignoring project type distribution-fragment - supportedProjectTypes = [hk2-jar, bundle]
[INFO]

Comment by janey [ 01/Nov/11 ]

can you try building with "mvn -Prelease-phase1 install" first and then "mvn install".

Jane

Comment by Veit Ullmann [ 01/Nov/11 ]

I tried building with "mvn -Prelease-phase1 install" first and then "mvn install".

This is the original error:

[ERROR] Failed to execute goal on project ejb-all: Could not resolve dependencies for project org.glassfish.ejb:ejb-all:pom:3.1.1: Could not find artifact org.glassfish.ejb:ejb-timer-databases:distribution-fragment:3.1.1 in glassfish-repo-archive (http://maven.glassfish.org/content/groups/glassfish) -> [Help 1]

I just commented the ejb-timer-databases:distribution-fragment in pom.xml of ejb-all and got the error with cmp-scripts:distribution-fragment:3.1.1.

The distribution-fragments seem to be the reasons for the problems, but how to fix this?

Comment by Snjezana Sevo-Zenzerovic [ 01/Nov/11 ]

Which Maven version is being used? IIRC, this was the same error we were running into with 3.1.1 workspace and Maven 3.x since distribution-fragment type modules were not being correctly resolved. Fix went into trunk workspace but 3.1.1 tag would still have the same issue. If that is the case, you'll need to build using Maven 2.2.x.

Comment by Veit Ullmann [ 02/Nov/11 ]

I used maven 3.0.3, o.k., I will try it with maven 2.2.1

Comment by Veit Ullmann [ 02/Nov/11 ]

Thank you, that worked!!!

Comment by scatari [ 07/Nov/11 ]

GlassFish 3.1.2 does not support maven 3.0.x.

Comment by Joe Di Pol [ 12/Dec/12 ]

worked with proper mvn version





[GLASSFISH-18640] Implement levelized build Created: 18/Apr/12  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Critical
Reporter: Sanjeeb Sahoo Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Since cloud components have been separated to a different directory under main, one should be able to build and promote main/appserver without having to build main/cloud. This is similar to how we are able to build and promote nucleus without having to build appserver or cloud.



 Comments   
Comment by Joe Di Pol [ 12/Dec/12 ]

cloud is no longer under main





[GLASSFISH-18670] Not a v4.0.0 POM. for project net.java:jvnet-parent Created: 01/May/12  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Major
Reporter: wbrana Assignee: Unassigned
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

svn co https://svn.java.net/svn/glassfish~svn/tags/3.1.2/
gfbuild.sh

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.glassfish.main:glassfish-parent:pom:3.1.2

Reason: Cannot find parent: net.java:jvnet-parent for project: org.glassfish.main:glassfish-parent:pom:3.1.2 for project org.glassfish.main:glassfish-parent:pom:3.1.2

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: net.java:jvnet-parent for project: org.glassfish.main:glassfish-parent:pom:3.1.2 for project org.glassfish.main:glassfish-parent:pom:3.1.2
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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 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 parent: net.java:jvnet-parent for project: org.glassfish.main:glassfish-parent:pom:3.1.2 for project org.glassfish.main:glassfish-parent:pom:3.1.2
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. for project net.java:jvnet-parent at /home/un/.m2/repository/net/java/jvnet-parent/1/jvnet-parent-1.pom
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1599)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:562)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
... 18 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Tue May 01 13:08:12 CEST 2012
[INFO] Final Memory: 1M/59M
[INFO] ------------------------------------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------

[INFO] Error building POM (may not be this project's POM).

cat /home/un/.m2/repository/net/java/jvnet-parent/1/jvnet-parent-1.pom
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/0.6.39</center>
</body>
</html>



 Comments   
Comment by wbrana [ 01/May/12 ]

Error was resolved by adding
<settings>
<mirrors>
<mirror>
<id>maven-central</id>
<url>http://repo1.maven.org/maven2/</url>
<mirrorOf>*,!eclipselink.repository</mirrorOf>
</mirror>
</mirrors>
</settings>





[GLASSFISH-18818] [main/cloud module built failed ]require org.glassfish.build:maven-glassfishbuild-extension:jar:3.2.3 Created: 22/Jun/12  Updated: 12/Dec/12  Resolved: 12/Dec/12

Status: Closed
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b42
Fix Version/s: None

Type: Bug Priority: Major
Reporter: TangYong Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP


Tags: building

 Description   

Maybe GF Team is resolving the building of main/cloud module.

Until now(2012/06/22), when I build the main/cloud module using "mvn -DskipTests=true clean install", building will be failed quickly.
-------------------------------------------------------------------------------------------------------------------------
[ERROR] The project org.glassfish.main.virtualization:libvirt-files:4.0-SNAPSHOT (E:\gfv4\trunk\main\cloud\iaas-mgmt-plugins\libvirt-files\pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin org.glassfish.build:maven-glassfishbuild-extension:3.2.3 or one of its dependencies could not be resolved: Failure to find org.glassfish.build:maven-glassfishbuild-extension:jar:3.2.3 in http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: distribution-base-zip @ line 56, column 16
[ERROR]
[ERROR] The project org.glassfish.main.virtualization:native-files:4.0-SNAPSHOT (E:\gfv4\trunk\main\cloud\iaas-mgmt-plugins\native-files\pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin org.glassfish.build:maven-glassfishbuild-extension:3.2.3 or one of its dependencies could not be resolved: Failure to find org.glassfish.build:maven-glassfishbuild-extension:jar:3.2.3 in http://repo1.maven.org/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of maven-central has elapsed or updates are forced -> [Help 2]
[ERROR] Unknown packaging: distribution-base-zip @ line 56, column 16
[ERROR]
[ERROR] The project org.glassfish.main.elasticity:elastic-metrics:4.0-SNAPSHOT (E:\gfv4\trunk\main\cloud\elasticity\elastic-metrics\pom.xml) has 3 errors
[ERROR] 'dependencies.dependency.version' for com.sun.jersey.contribs:jersey-multipart:jar is missing. @ line 88, column 21
[ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-client:jar is missing. @ line 92, column 21
[ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-json:jar is missing. @ line 96, column 21
[ERROR]
-------------------------------------------------------------------------------------------------------------------------

The reason is that "org.glassfish.build:maven-glassfishbuild-extension:jar:3.2.3" is not found from http://repo1.maven.org/maven2/ .

I found that on http://repo1.maven.org/maven2/, the recent version of maven-glassfishbuild-extension is 3.2.2.

I have forgotten when glassfishbuild.version in trunk\main\pom.xml is updated to 3.2.3. Of course, I think that if I build the trunk\glassfishbuild\maven-glassfishbuild-extension subproject myself, maybe main/cloud module can be successful.

In addition,in trunk\main\pom.xml, main/cloud module is not put in build process. Whether this is related to http://java.net/jira/browse/GLASSFISH-18640 or not?



 Comments   
Comment by TangYong [ 27/Jun/12 ]

The problem does not exist in the newest gf trunk.

After I updated the gf trunk, main/cloud directory has not existed.

Please close the issue, thanks very much!

Comment by Joe Di Pol [ 12/Dec/12 ]

cloud no longer exists in trunk.





[GLASSFISH-18851] cloud-extra module built failed Created: 27/Jun/12  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Major
Reporter: TangYong Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP



 Description   

After updating the gf/trunk/main, when I attempt to build main/cloud-extra module, the following error happened.

E:\gfv4\trunk\main\cloud-extra>mvn -DskipTests=true clean install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.glassfish.main.elasticity:elastic-metrics:4.0-SNAPSHOT (E:\gfv4\trunk\main\cloud-extra\elasticity\elastic-metrics\pom.xml) has 3 errors
[ERROR] 'dependencies.dependency.version' for com.sun.jersey.contribs:jersey-multipart:jar is missing. @ line 88, column 21
[ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-client:jar is missing. @ line 92, column 21
[ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-json:jar is missing. @ line 96, column 21
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

The reason is that in elastic-metrics\pom.xml, the following dependency declarings missed versions.

<dependency>
<groupId>com.sun.jersey.contribs</groupId>
<artifactId>jersey-multipart</artifactId>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-client</artifactId>
</dependency>
<dependency>
<groupId>com.sun.jersey</groupId>
<artifactId>jersey-json</artifactId>
<exclusions>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
</exclusion>
</exclusions>
</dependency>

The declaring of above dependency version should be put in main/pom.xml, however, in main/pom.xml, I also did not find them.



 Comments   
Comment by TangYong [ 27/Jun/12 ]

Because the current jersey is 2.0-m05, whether team is considering replacing com.sun.jersey(jersey 1.x) with org.glassfish.jersey(jersey 2.x) or not.After all,
all the internal Jersey API’s underwent a significant refactoring in Jersey 2.0.

However, I want to know whether because of jersey 2.x main/cloud-extra's building process
will be blocked or not.

Comment by TangYong [ 27/Jun/12 ]

In addition, the following problems also happened in building.

1 "cloud-extra\tenant-manager\src\main\java\org\glassfish\paas\tenantmanager\cli\impl\TenantDataMutatorAdminCommandContext" needs to implement AdminCommandContext.getProgressStatus().

maybe http://java.net/jira/browse/GLASSFISH-12032 is related to the this.

2 In "org\glassfish\paas\tenantmanager\apiTenantManagerTest.java", the following codes

Assert.assertEquals("Next Id", 1, environments.allocateId());
Assert.assertEquals("Next Id", 2, environments.allocateId());

have problems. Should be replaced with the following codes:

Assert.assertEquals("Next Id", 1, environments.allocateId().longValue());
Assert.assertEquals("Next Id", 2, environments.allocateId().longValue());

Comment by Joe Di Pol [ 12/Dec/12 ]

cloud-extra has been removed from the trunk, so this bug is no longer valid.





[GLASSFISH-18367] Names Chopped Off of distribution web page Created: 15/Feb/12  Updated: 12/Dec/12  Resolved: 12/Dec/12

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

Type: Bug Priority: Major
Reporter: Byron Nevins Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File display.jpg    
Tags: 3_1_2-exclude

 Description   

This has been driving me nuts since forever. I finally decided to create an issue.

Take a look at the jpg. There is gigantic "real estate" available but it is completely ignored. Every single filename is chopped off.

I have to slowly, ever so slowly, hover over every filename to see the tool tip of what the actual filename is in order to get the right one!

Perhaps change the final filenames so at least, say, the name starts with the platform name?

Note how every truncated name looks exactly the same on the image attached.



 Comments   
Comment by Joe Di Pol [ 12/Dec/12 ]

The formatting is determined by the javaweb.us.oracle.com web server, and we're not changing the bundle names because if its limitations.





[GLASSFISH-17173] Build Errors on Java SE 7 Created: 09/Aug/11  Updated: 12/Dec/12  Resolved: 12/Dec/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Critical
Reporter: Byron Nevins Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_x-exclude

 Description   

Isn't it time to solve this? GF can not be built using Java SE7. I am constantly going back and forth between 6 and 7 because of this.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.glassfish.hk2:hk2-maven-plugin:1.6.12:hk2-compile': Unable to load the mojo 'org.glassfish.hk2:hk2-maven-plugin:1.6.12:hk2-compile' in the plugin 'org.glassfish.hk2:hk2-maven-plugin'. A required class is missing: com/sun/mirror/apt/AnnotationProcessorFactory
com.sun.mirror.apt.AnnotationProcessorFactory



 Comments   
Comment by scatari [ 07/Nov/11 ]

GlassFish 3.1.x will not be built with JDK 7 to support compatibility.

Comment by Joe Di Pol [ 12/Dec/12 ]

This has been fixed in the 4.0 trunk.





[GLASSFISH-19181] Upgrade the GlassFish codebase to require use of Java 7 Created: 18/Oct/12  Updated: 10/Dec/12  Resolved: 10/Dec/12

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

Type: Improvement Priority: Major
Reporter: Nigel Deakin Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks MQ-169 Make Connection and other interfaces ... Closed
blocks MQ-191 Migrate the MQ 5.0 codebase to compil... Closed

 Description   

GlassFish needs to be upgraded to allow the use of Java 7. In particular it must allow a version of MQ to be integrated which uses Java 7.

MQ-191 is dependent on this.



 Comments   
Comment by marina vatkina [ 18/Oct/12 ]

GLASSFISH-19133 also depends on JDK 7

Comment by Tom Mueller [ 18/Oct/12 ]

This is required for the Java EE 7 RI/SDK

Comment by Tom Mueller [ 18/Oct/12 ]

GlassFish already allows the use of Java SE 7, however, it builds with -source 1.6 and -target 1.6.

The purpose of this issue to start building the appserver part of glassfish with -source 1.7 and -target 1.7 and to require that GlassFish be run with Java SE 7 (currently only Java SE 6 is enforced at runtime).
So there is a build aspect to this and a runtime aspect.

Comment by Romain Grécourt [ 10/Dec/12 ]

See svn rev #57168





[GLASSFISH-19279] Build Java EE 7 javadocs Created: 02/Nov/12  Updated: 10/Dec/12  Resolved: 10/Dec/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b61
Fix Version/s: 4.0_b65

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

Issue Links:
Dependency
blocks GLASSFISH-19280 Include Java EE 7 javadocs in installer Resolved
Related
is related to GLASSFISH-19259 Java EE 7: javaee-api.jar Resolved

 Description   

We need to start generating Java EE 7 javadocs as part of our build process.



 Comments   
Comment by Romain Grécourt [ 02/Nov/12 ]

new build process and new workspace is needed. This is not going to be done under the glassfish workspace.

Comment by Romain Grécourt [ 10/Dec/12 ]

See http://dlc.sun.com.edgesuite.net/glassfish/4.0/promoted/javaee-api-7.0-b65-javadoc.jar





[GLASSFISH-17329] hk2:hk2-compile fails under JDK 7 Created: 21/Sep/11  Updated: 20/Oct/12  Resolved: 20/Oct/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: 4.0_b36

Type: Bug Priority: Major
Reporter: jglick Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://svn.java.net/svn/glassfish~svn/trunk/main @49207, JDK 7 (GA), Ubuntu 10.04, Maven 3.0.3


Issue Links:
Related
is related to STAPLER-14 stapler:apt-compile fails under JDK 7 Resolved
Tags: 3_1_2-exclude

 Description   
[INFO] --- hk2-maven-plugin:1.6.17:hk2-compile (default-hk2-compile) @ scattered-archive-api ---
Sep 21, 2011 12:27:15 PM org.sonatype.guice.bean.reflect.LoadedClass
WARNING: Error injecting: com.sun.enterprise.module.maven.HK2CompileMojo
java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
	at java.lang.Class.getDeclaredConstructors0(Native Method)
	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2404)
	at java.lang.Class.getDeclaredConstructors(Class.java:1853)
	at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:243)
	at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:96)
	at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:628)
	at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:835)
	at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:769)
	at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:254)
	at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:205)
	at com.google.inject.internal.InjectorImpl.getInternalFactory(InjectorImpl.java:843)
	at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:957)
	at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:990)
	at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:951)
	at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1003)
	at org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:47)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
	at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:968)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1014)
	at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:964)
	at com.google.inject.Scopes$1$1.get(Scopes.java:59)
	at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:79)
	at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:53)
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243)
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235)
	at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:455)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:92)
	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:319)
	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: java.lang.ClassNotFoundException: com.sun.mirror.apt.AnnotationProcessorFactory
	at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
	... 47 more
....
[ERROR] Failed to execute goal org.glassfish.hk2:hk2-maven-plugin:1.6.17:hk2-compile (default-hk2-compile) on project scattered-archive-api: Execution default-hk2-compile of goal org.glassfish.hk2:hk2-maven-plugin:1.6.17:hk2-compile failed: Unable to load the mojo 'hk2-compile' in the plugin 'org.glassfish.hk2:hk2-maven-plugin:1.6.17'. A required class is missing: com/sun/mirror/apt/AnnotationProcessorFactory

Similar to STAPLER-14. Workaround is to build using JDK 6.



 Comments   
Comment by Romain Grécourt [ 21/Sep/11 ]

There is an issue for JDK7 and GlassFish reported here

The fix was included in version 1.6.18 of HK2, I see in the snippet you provided that the version 1.6.17 is used.
The version used currently in the trunk is 1.6.19, have you updated your workspace?

Comment by jglick [ 27/Sep/11 ]

OK, close as duplicate then. (I do not have permissions to do so.) Build seems to work using current trunk (49992) with JDK 7, Maven 3.0.3, -DskipTests.

Comment by jglick [ 27/Sep/11 ]

Or at least up to a seemingly unrelated error:

nucleus/core/kernel/src/main/java/com/sun/enterprise/v3/server/AppServerStartup.java:63: error: cannot find symbol
import org.glassfish.hk2.Bindings;
                        ^
Comment by scatari [ 02/Nov/11 ]

3.1.2 cannot be compiled with JDK 7 for backward compatibility.





[GLASSFISH-18595] Could not resolve dependencies when building with Maven 3 Created: 04/Apr/12  Updated: 07/Apr/12  Resolved: 07/Apr/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0_b30
Fix Version/s: 4.0_b31

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


 Description   

When building with Maven 3 and not referencing the internal GlassFish Nexus (gf-maven.us.oracle.com), build fails when the following message:

[ERROR] Failed to execute goal on project glassfish-osgi: Could not resolve dependencies for project org.glassfish.packager:glassfish-osgi:distribution-base-zip:4.0-SNAPSHOT: Could not find artifact org.eclipse.persistence:javax.persistence:jar:2.0.4.v201112200901 in maven-central (http://repo1.maven.org/maven2/) -> [Help 1]



 Comments   
Comment by janey [ 04/Apr/12 ]

Even though org.eclipse.persistence:javax.persistence:jar:2.0.4.v201112200901 is already available in local repo, Maven 3 still tries to find it from central.

Comment by janey [ 07/Apr/12 ]

This is fixed by svn rev 53391.

The latest version of osgi-ejb-container:1.0.1 and osgi-web-container:1.0.3 references a new module-parent-pom:1.0.3 which has the EclipseLink repository defined.





[GLASSFISH-17285] Support building with Java SE 7 Created: 09/Sep/11  Updated: 02/Apr/12  Resolved: 02/Apr/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: 4.0_b30

Type: Bug Priority: Major
Reporter: Byron Nevins Assignee: Romain Grécourt
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: GZip Archive building_gf_with_jdk7_changes.tar.gz     File glassfish_tests_ignores-update1.diff     File glassfish_tests_ignores-update2.diff     File glassfish_tests_ignores-update3.diff     File glassfish_tests_ignores-update4.diff     File glassfish_tests_ignores.diff    
Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17306 Unit tests that fail randomly (glassf... Sub-task Resolved Cheng Fang  
GLASSFISH-17307 Unit tests that fail randomly (appser... Sub-task Resolved Jagadish  
GLASSFISH-17316 Unit tests that fail randomly (orb-co... Sub-task Resolved Harshad Vilekar  
GLASSFISH-17317 Unit tests that fail randomly (core/k... Sub-task Closed Romain Grécourt  
GLASSFISH-17318 Unit tests that fail randomly (jdbc/a... Sub-task Resolved Jennifer Chou  
Tags: 3_1_2-exclude, GlassFish, JDK7, Java7, JavaSE7

 Description   

If you try to build GlassFish with JDK7 you will probably scratch your head wondering what the problem is. It's one of those situations where you have to have a mental mapping like this:

<Enormous Weird Bizarre Error Message about HK2> ===> You forgot to set your JDK back to 6!!

=======
Instead why not simply FORBID compiling with 7 – then we will get a nice error message that says exactly what the problem is?

Eventually when the problem is fixed – remove the restriction.

Here is the actual compile error:

[INFO] Building in d:\gf\main\nucleus\common\common-util
[INFO] ------------------------------------------------------------------------
[INFO] [antrun:run

{execution: default}

]
[INFO] Executing tasks
[delete] Deleting: D:\gf\main\nucleus\common\common-util\src\main\java\com\sun\appserv\server\util\Version.java
[copy] Copying 1 file to D:\gf\main\nucleus\common\common-util\src\main\java\com\sun\appserv\server\util
[INFO] Executed tasks
[INFO] [resources:resources

{execution: default-resources}

]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 22 resources
-----------------------------------------------------
this realm = app0.child-container[org.glassfish.hk2:hk2-maven-plugin:1.6.17]
urls[0] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/hk2-maven-plugin/1.6.17/hk2-maven-plugin-1.6.17.jar
urls[1] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/hk2-maven/1.6.17/hk2-maven-1.6.17.jar
urls[2] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/hk2-core/1.6.17/hk2-core-1.6.17.jar
urls[3] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/class-model/1.6.17/class-model-1.6.17.jar
urls[4] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/config/1.6.17/config-1.6.17.jar
urls[5] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/auto-depends/1.6.17/auto-depends-1.6.17.jar
urls[6] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/external/javax.inject/1.6.17/javax.inject-1.6.17.jar
urls[7] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/external/asm-all-repackaged/1.6.17/asm-all-repackaged-1.6.17.jar
urls[8] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/hk2-api/1.6.17/hk2-api-1.6.17.jar
urls[9] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/osgi-resource-locator/1.0.1/osgi-resource-locator-1.0.1.jar
urls[10] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/jvnet/tiger-types/1.4/tiger-types-1.4.jar
urls[11] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/external/bean-validator/1.6.17/bean-validator-1.6.17.jar
urls[12] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/com/googlecode/jtype/jtype/0.1.0/jtype-0.1.0.jar
urls[13] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.jar
urls[14] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/maven/maven-archiver/2.0.4/maven-archiver-2.0.4.jar
urls[15] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-4/plexus-archiver-1.0-alpha-4.jar
urls[16] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/osgi/osgi_R4_core/1.0/osgi_R4_core-1.0.jar
urls[17] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/hk2-dependency-verifier/1.6.17/hk2-dependency-verifier-1.6.17.jar
urls[18] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/osgi-adapter/1.6.17/osgi-adapter-1.6.17.jar
urls[19] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/bcel/bcel/5.2/bcel-5.2.jar
urls[20] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/config-generator/1.6.17/config-generator-1.6.17.jar
urls[21] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/glassfish/hk2/auto-depends-plugin/1.6.17/auto-depends-plugin-1.6.17.jar
urls[22] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/com/sun/xml/bind/jaxb-xjc/2.1.3/jaxb-xjc-2.1.3.jar
urls[23] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.3/jaxb-impl-2.1.3.jar
urls[24] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar
urls[25] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/javax/xml/stream/stax-api/1.0/stax-api-1.0.jar
urls[26] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
urls[27] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/com/sun/xml/stream/sjsxp/1.0/sjsxp-1.0.jar
urls[28] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.0.2/maven-compiler-plugin-2.0.2.jar
urls[29] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/codehaus/plexus/plexus-compiler-api/1.5.3/plexus-compiler-api-1.5.3.jar
urls[30] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/codehaus/plexus/plexus-compiler-manager/1.5.3/plexus-compiler-manager-1.5.3.jar
urls[31] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/codehaus/plexus/plexus-compiler-javac/1.5.3/plexus-compiler-javac-1.5.3.jar
urls[32] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
urls[33] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
urls[34] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/org/apache/maven/shared/maven-osgi/0.2.0/maven-osgi-0.2.0.jar
urls[35] = file:/C:/Users/wnevins.ST-USERS/.m2/repository/biz/aQute/bndlib/0.0.203/bndlib-0.0.203.jar
Number of imports: 10
import: org.codehaus.classworlds.Entry@a6c57a42
import: org.codehaus.classworlds.Entry@12f43f3b
import: org.codehaus.classworlds.Entry@20025374
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@92758522
import: org.codehaus.classworlds.Entry@ebf2705b
import: org.codehaus.classworlds.Entry@bb25e54
import: org.codehaus.classworlds.Entry@bece5185
import: org.codehaus.classworlds.Entry@3fee8e37
import: org.codehaus.classworlds.Entry@3fee19d8

this realm = plexus.core
urls[0] = file:/C:/bin/apache-maven-2.2.1/bin/../lib/maven-2.2.1-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.Entry@a6c57a42
import: org.codehaus.classworlds.Entry@12f43f3b
import: org.codehaus.classworlds.Entry@20025374
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@92758522
import: org.codehaus.classworlds.Entry@ebf2705b
import: org.codehaus.classworlds.Entry@bb25e54
import: org.codehaus.classworlds.Entry@bece5185
import: org.codehaus.classworlds.Entry@3fee8e37
import: org.codehaus.classworlds.Entry@3fee19d8
-----------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.glassfish.hk2:hk2-maven-plugin:1.6.17:hk2-compile': Unable to load the mojo 'org.glass
fish.hk2:hk2-maven-plugin:1.6.17:hk2-compile' in the plugin 'org.glassfish.hk2:hk2-maven-plugin'. A required class is missing: com/sun/mirror/apt/Anno
tationProcessorFactory
com.sun.mirror.apt.AnnotationProcessorFactory
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Fri Sep 09 11:48:33 PDT 2011
[INFO] Final Memory: 33M/245M
[INFO] ------------------------------------------------------------------------



 Comments   
Comment by janey [ 12/Sep/11 ]

Assign to Romain. He is working on this and has made good progress.

Comment by Romain Grécourt [ 16/Sep/11 ]

Here are all the changes made in HK2,glassfishbuild and GlassFish (see building_gf_with_jdk7_changes.tar.gz) in order to have the GlassFish workspace buildable with the JDK7. New versions of HK2 (1.6.18) and glassfishbuild (3.2.2) have been released, they are now used in the GlassFish trunk (see r49613).

Furthermore the GlassFish workspace still requires some workaround to build from scratch with the JDK7 because of some unit tests that fail randomly (see http://wiki.apidesign.org/wiki/OrderOfElements#JUnit_and_Switch_to_JDK7). You can use the attached diff file to avoid these unit tests and so build GlassFish from scratch with JDK7.

I'll create separate issues for each of these unit tests.

Comment by Romain Grécourt [ 16/Sep/11 ]

The behavior observed regarding the unit tests that fail is random. Even if I was able to build several times (about 10 times) from scratch with the first set of ignores, I discovered a new one just after having updated the issue...

Here is a diff file to ignores these failing tests (glassfish_tests_ignores-update1.diff), available as attachment.

Comment by Romain Grécourt [ 19/Sep/11 ]

since Cheng resolve one the subtask #17306 (unit tests from nucleus/common/glassfish-naming) the set of ignores changed. Here is a new update of the ignore diff file that can be used with revison 49672 and above (glassfish_tests_ignores-update2.diff available as attachment).

Comment by Romain Grécourt [ 19/Sep/11 ]

Reopened the sub task #17306 as some other unit test from nucleus/common/glassfish-naming are failing.

I've found a way to reproduce the issues each time by running the test methods individually.

$ cd [glassfishWorkspace]/[module]
$ mvn -Dtest=fullClassName#testMethodName org.apache.maven.plugins:maven-surefire-plugin:2.8:test

You must use a version of the surefire plugin greater or equals to 2.7.3. For more information see this link

Comment by Romain Grécourt [ 19/Sep/11 ]

Last diff file for ignoring the unit tests. (glassfish_tests_ignores-update3.diff)

Comment by Romain Grécourt [ 23/Feb/12 ]

attaching last version of the diff file to ignore the unit test.

Comment by Romain Grécourt [ 02/Apr/12 ]

GlassFish trunk is build-able with JDK7 since revision #53208 (03/28/12).





[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-8380] Java files should not be treated as binary! Created: 18/May/09  Updated: 07/Mar/12  Resolved: 07/Mar/12

Status: Closed
Project: glassfish
Component/s: build_system
Affects Version/s: 9.0pe
Fix Version/s: future release

Type: Bug Priority: Minor
Reporter: Byron Nevins Assignee: janey
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 8,380
Status Whiteboard:

v2.1.1_exclude


 Description   

SUMMARY:

There are many many java/properties/xml/etc. files in the subversion repository
that have a LF hard-wired at the end of every line. I*.e. they are setup as
binary files and were checked in originally from *NIX. When such a file is
checked out in WIndows – you see one huge mega line. If you check it back in
from Windows then UNIX users will see a CR (^M) on EVERY line.

I'm guessing that our Subversion repository automatically sets all ascii files
to binary. I fix this problem piecemeal here and there as I see it like so:

svn propset svn-eol-style native somefile.java

If I happen to miss it then it causes an annoying diff to be present forever. I
ended up getting an Issue assigned to me because the "unreal" diffs made it
appear that I completely rewrote a class when I only changed a few lines.

At the bottom of this description is an example. The standard svn diff shows
that EVERY line in the file changed. In reality 4 lines or so were changed.
ref: https://glassfish.dev.java.net/issues/show_bug.cgi?id=7942

      • This issue should be fixed like so:

1) Set all existing ascii files in the repository
2) make the default eol-style == native for all new ascii files

svn diff -r 25743:25744
https://svn.dev.java.net/svn/glassfish-svn/trunk/v3/web/web-glue/src/main/java/com/sun/enterprise/web/WebModule.java



 Comments   
Comment by kumara [ 14/Sep/09 ]

-> janey

Comment by Ed Bratt [ 15/Oct/09 ]

Will not fix in v2.1.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.

Comment by janey [ 07/Mar/12 ]

A Hudson job is setup to check all the files in trunk workspace and add svn property svn:eol-style=native to new text files added in GlassFish main workspace.





[GLASSFISH-5005] Provide md5 hashes for downloads Created: 11/May/08  Updated: 07/Mar/12  Resolved: 07/Mar/12

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

Type: Improvement Priority: Major
Reporter: writtmeyer Assignee: janey
Resolution: Invalid 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,005

 Description   

Right now there are no md5 values on the download pages. These should be added
to enable the user to verify its download.

E.g. there was a mail on the users mailing list today that most probably had to
do with a corrupted download. The user would have been able to spot this issue
if he had an md5 value available.



 Comments   
Comment by Snjezana Sevo-Zenzerovic [ 12/May/08 ]

Moving to more appropriate subcomponent.

Comment by writtmeyer [ 26/Oct/09 ]

This issue has been filed originally for v2.1. But it is still relevant for the
v3 download page as well as for the promoted download page. Thus I've changed
the version to v3.

Comment by Snjezana Sevo-Zenzerovic [ 13/Nov/09 ]

...

Comment by janey [ 13/Nov/09 ]

Please provide the URLs to the download page.
The artifacts in maven repository have the md5 files.

Comment by Snjezana Sevo-Zenzerovic [ 13/Nov/09 ]

Jane,

this RFE is for GF download artifacts, not maven artifacts. All of download URLs
referenced here:

https://glassfish.dev.java.net/public/downloadsindex.html#top

could use hashsum files....

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 ]

dev.java.net is no longer available.





[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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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.





Support building with Java SE 7 (GLASSFISH-17285)

[GLASSFISH-17318] Unit tests that fail randomly (jdbc/admin) when using JDK7 to build GlassFish from scratch Created: 19/Sep/11  Updated: 29/Feb/12  Resolved: 29/Feb/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Sub-task Priority: Major
Reporter: Romain Grécourt Assignee: Jennifer Chou
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubutu 11.04 (2.6.38-11-generic) ; JDK 1.7.0 ; Maven 2.2.1


Attachments: File glassfish_tests_ignores-update3_without_jdbc-admin.diff    
Tags: JDK7, JUnit, jdbc

 Description   

Some unit tests from "jdbc/admin" are failing when using JDK7.

When trying to build the GlassFish workspace with JDK7 from scratch (from top level directory), the build fails because of some unit tests. According to the following link it seems that these unit tests depends somehow on the order of invocation.

The behavior is quite random because the unit tests don't fail when you run "mvn clean install" from the appropriate module. Also I've tried several times to build from scratch (i.e. on a fresh checkout) and the tests that fail can be different each time.

Here is a diff file available as attachment that disable other failing tests so it will be easier to reproduce the bug. For your information: I've reproduced the bug 3 times in 4 trials from fresh checkout + patch.
===============================================================================================================================

  • Here is the outputs from Maven:

===============================================================================================================================

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.JavaConfig)
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.Server)
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.config.ConfigParser handleElement
SEVERE: Ignoring unrecognized element management-rules at Line number = 156
Column number = 40
System Id = file:/home/romano/workspaces/glassfish/main-scratch-jdk7_28/appserver/jdbc/admin/target/test-classes/DomainTest.xml
Public Id = null
Location Uri= file:/home/romano/workspaces/glassfish/main-scratch-jdk7_28/appserver/jdbc/admin/target/test-classes/DomainTest.xml
CharacterOffset = 10705

Sep 19, 2011 4:13:57 PM org.hibernate.validator.util.Version <clinit>
INFO: Hibernate Validator 4.1.0.Final
Sep 19, 2011 4:13:57 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
Tests run: 6, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 0.46 sec <<< FAILURE!
Running org.glassfish.jdbc.admin.cli.TestDocument
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec
Running org.glassfish.jdbc.admin.cli.CreateJdbcResourceTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.044 sec
Running org.glassfish.jdbc.admin.cli.DeleteJdbcResourceTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.041 sec
Running org.glassfish.jdbc.config.JdbcConnectionPoolValidationTest
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.JavaConfig)
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.Server)
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.glassfish.jdbc.config.JdbcConnectionPoolDefaultsTest
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.JavaConfig)
Sep 19, 2011 4:13:57 PM org.jvnet.hk2.component.ContractLocatorImpl warnOnUsage
WARNING: name and scope are currently only appropriate for byContract usage; (name: default-instance-name; type: com.sun.enterprise.config.serverbeans.Server)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
Running org.glassfish.jdbc.config.ConcurrentModificationsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec

Results :

Failed tests: 
  testExecuteSuccessListNoBob(org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest)

Tests run: 23, Failures: 1, Errors: 0, Skipped: 7

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to /home/romano/workspaces/glassfish/main-scratch-jdk7_28/appserver/jdbc/admin/target/surefire-reports for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 21 seconds
[INFO] Finished at: Mon Sep 19 16:13:57 CEST 2011
[INFO] Final Memory: 403M/752M
[INFO] ------------------------------------------------------------------------

===============================================================================================================================

  • Here is the surfire report:

===============================================================================================================================

romano@frenchfish:~/workspaces/glassfish/main-scratch-jdk7_28$ cat appserver/jdbc/admin/target/surefire-reports/*.txt
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.admin.cli.CreateJdbcResourceTest
-------------------------------------------------------------------------------
Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.044 sec
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.admin.cli.DeleteJdbcResourceTest
-------------------------------------------------------------------------------
Tests run: 6, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0.041 sec
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest
-------------------------------------------------------------------------------
Tests run: 6, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 0.46 sec <<< FAILURE!
testExecuteSuccessListNoBob(org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest)  Time elapsed: 0.01 sec  <<< FAILURE!
java.lang.AssertionError: expected:<SUCCESS> but was:<FAILURE>
	at org.junit.Assert.fail(Assert.java:71)
	at org.junit.Assert.failNotEquals(Assert.java:451)
	at org.junit.Assert.assertEquals(Assert.java:99)
	at org.junit.Assert.assertEquals(Assert.java:116)
	at org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest.testExecuteSuccessListNoBob(ListJdbcResourcesTest.java:235)
	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.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
	at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
	at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
	at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
	at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
	at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
	at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
	at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
	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.runSuitesInProcess(SurefireBooter.java:345)
	at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:241)
	at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:537)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
	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.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)

-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.admin.cli.TestDocument
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.config.ConcurrentModificationsTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.config.JdbcConnectionPoolDefaultsTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
-------------------------------------------------------------------------------
Test set: org.glassfish.jdbc.config.JdbcConnectionPoolValidationTest
-------------------------------------------------------------------------------
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec


 Comments   
Comment by Romain Grécourt [ 19/Sep/11 ]

attaching patch to reproduce the bug.

Comment by Romain Grécourt [ 19/Sep/11 ]

As the issue can be only seen when building from top level directory (which can be very long), you may want to use the following steps:

$ cd [glassfishWorkspace]/appserver/jdbc/admin
$ mvn -Dtest=org.glassfish.jdbc.admin.cli.ListJdbcResourcesTest#testExecuteSuccessListNoBob org.apache.maven.plugins:maven-surefire-plugin:2.8:test

You must use a version of the surefire plugin greater or equals to 2.7.3. For more information see this link

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

changing versions.

Comment by Tom Mueller [ 19/Dec/11 ]

Note, this issue is actually for jdbc/admin even though the description says "orb/orb-connector" at the top.

Comment by Romain Grécourt [ 19/Dec/11 ]

removing mistake in description.

Comment by Shalini [ 26/Dec/11 ]

Assignin