Bug 326891

Comment 1 Denis Roy 2010-10-04 08:40:52 EDT

The new Build server is no longer a PPC box.  It's an x86_64, so you cannot use the ppc binaries anymore.

Please use one of the following in /opt/public/common/

ibm-java-x86_64-60
jdk-1.5.0_16
jdk-1.5.0-22.x86_64
jdk-1.6.0_10
jdk-1.6.x86_64
sun-jdk1.6.0_21_i586
sun-jdk1.6.0_21_x64

Comment 2 Ashwani Kr Sharma 2010-10-05 00:03:50 EDT

Hi,

I tried using now jdk-1.5.0_16, jdk-1.6.0_10 and sun-jdk1.6.0_21_x64.
But non of them have pack200 program. Hence, the build fails: https://hudson.eclipse.org/hudson/job/cbi-emf-query2-0.7/

Following is warning reported in : /opt/users/hudsonbuild/workspace/cbi-emf-query2-0.7/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml
-----------------------------------
Warning!
Could not find pack200 executable
	in ${JAVA_HOME},
	in ${JAVA60_HOME} or
	in ${JAVA50_HOME}
No packed jars (.jar.pack.gz) will be produced for this build.
-----------------------------------


How can this be corrected ?
Which JDK should i use ?

Regards,
Ashwani Kr Sharma

Comment 3 David Williams 2010-10-09 04:02:54 EDT

They are there in at least some. 
You will almost certainly want to use 1.5, so I'll only list those:

/opt/public/common/jdk-1.5.0_16/bin/pack200
/opt/public/common/jdk-1.5.0_16/jre/bin/pack200
/opt/public/common/jdk-1.5.0-22.x86_64/bin/pack200
/opt/public/common/jdk-1.5.0-22.x86_64/jre/bin/pack200

I could not get or see the buildAllHelper.xml file, so I am not sure that it says, but off hand, I'd think that if it was printing out something like 

Could not find pack200 executable
    in ${JAVA_HOME}

Then that's mean that ${JAVA_HOME} was not defined for this script (or, not being passed in to. I'd guess the message wants to say something like

Could not find pack200 executable
    in /opt/public/common/jdk-1.5.0_16/


But, note sure. 

HTH

Comment 4 Ashwani Kr Sharma 2010-10-09 06:02:44 EDT

Hi,

These JDK constants are defined in build.properties file.
--------------------------------------------------------------
JAVA_HOME=/opt/public/common/jdk-1.5.0_16
JAVA50_HOME=/opt/public/common/jdk-1.5.0_16
JAVA60_HOME=/opt/public/common/sun-jdk1.6.0_21_x64
--------------------------------------------------------------

The build.properties files is included in build.xml as following:
--------------------------------------------------------------
<property file="build.properties" />
--------------------------------------------------------------
Hence, i think the values are picked from the properties file.

Also, i saw the console output for the job. It has this entry which means the jdk is picked.
---------------------------------------------------------------
oad.properties:
     [echo] Load properties from /opt/users/hudsonbuild/workspace/cbi-emf-query2-0.7/build/org.eclipse.query2.releng/build.properties
     [echo] 
     [echo] Loaded JAVA*_HOME and bootclasspath values:
     [echo]         JAVA_HOME = /opt/public/common/jdk-1.5.0_16
----------------------------------------------------------------

Earlier the build path was incorrect and even compilation was not happening. But when i corrected the JDK paths, build is happening but archiving failes. (as seen in build results of the job)

The releng related files are located here:
/cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.query/prototypes/releng/org.eclipse.emf.query2.releng

The buildAllHelper.xml is located here:
https://hudson.eclipse.org/hudson/job/cbi-emf-query2-0.7/ws/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml

Regards,
Ashwani Kr Sharma

Comment 5 Ashwani Kr Sharma 2010-10-09 06:15:29 EDT

Hi,

I specified PACK200_JAVA_HOME explicitly. Now, PACK200 is getting picked up.
Hence, i am closing the issue.

Thanks for your support.

Best Regards,
Ashwani Kr Sharma