Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334141 - java.beans.Introspector not found during compilation in recent builds
Summary: java.beans.Introspector not found during compilation in recent builds
Status: RESOLVED FIXED
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-12 12:32 EST by David Williams CLA
Modified: 2011-01-12 13:00 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2011-01-12 12:32:47 EST
The Dali project recently started using the subject class in org.eclipse.jpt.jaxb.core.tests and getting mysterious compilation problems during a build. 

It turns out, this bundle specifies a BREE of JavaSE-1.6 and in 1.6, the IBM Java VM (the one whose libraries we compile against) moved this Instrospector class (and others) out into their own "beans.jar". 

So, the fix was to add beans.jar to the  PDE classpath which for production we specify in runbuild.xml: 

        <property
            name="JavaSE-1.6"
            value="${env.JAVA_6_HOME}/jre/lib/rt.jar:${env.JAVA_6_HOME}/jre/lib/vm.jar:${env.JAVA_6_HOME}/jre/lib/java.util.jar:${env.JAVA_6_HOME}/jre/lib/xml.jar:${env.JAVA_6_HOME}/jre/lib/graphics.jar:${env.JAVA_6_HOME}/jre/lib/server.jar:${env.JAVA_6_HOME}/jre/lib/ibmorbapi.jar:${env.JAVA_6_HOME}/jre/lib/security.jar:${env.JAVA_6_HOME}/jre/lib/ibmpkcs.jar:${env.JAVA_6_HOME}/jre/lib/ibmjcefw.jar:${env.JAVA_6_HOME}/jre/lib/beans.jar"/>
Comment 1 David Williams CLA 2011-01-12 12:33:23 EST
fixed as described in previous comment.
Comment 2 David Williams CLA 2011-01-12 13:00:16 EST
Neil, Tran Le, just documenting here the recent issue we discussed via email ... for future reference if ever needed ... and serve as a reminder when mysterious compile errors happen in the future ... since you guys are always on the bleeding edge of using new things from the VM :) 

As I've stated before, I'd prefer to only add jars "as needed" for fear of adding something sort of non-standard ... but would reconsider if there is other opinions. 

For the record, there's 33 jars in /jre/lib (in IBM's Java 6 VM)

annotation.jar
ibmcertpathfw.jar
ibmjgssfw.jar
ibmorbapi.jar
ibmxmlcrypto.jar
javaws.jar
management-agent.jar
security.jar
xml.jar
beans.jar
ibmcertpathprovider.jar
ibmjgssprovider.jar
ibmorb.jar
j9zip.jar
jlm.jar
plugin.jar
sql.jar
charsets.jar
ibmcfw.jar
ibmjssefw.jar
ibmpkcs.jar
javascript.jar
jndi.jar
resources.jar
vm.jar
deploy.jar
ibmjcefw.jar
ibmjsseprovider2.jar
ibmsaslfw.jar
java.util.jar
logging.jar
rt.jar
xmldsigfw.jar


And we are currently using 11 of them. 


rt.jar
vm.jar
java.util.jar
xml.jar
graphics.jar
server.jar
ibmorbapi.jar
security.jar
ibmpkcs.jar
ibmjcefw.jar
beans.jar


Well ... now that I've written them out ... I see that server.jar and graphics.jar are no longer in the Java 6 VM ... so that was useful ... so I'll remove them from the PDE classpath list (but will let current build finish). Those jars _are_ in 1.4 and 1.5 ... I just blindly copied them over to 1.6. From a casual glance, it appears what ever was in graphics.jar and server.jar was moved to the (new) rt.jar in 1.6.