Re: [equinox-dev] [prov] manifest changes
I have reverted this change and also gone through the p2 bundles to ensure that the EEs are set correctly. There is currently a problem in the way that we compute the classpath w.r.t. EEs so we need to leave the higher EEs first in the manifest for now. For reference, the bug is described here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=219979 Also it is important to note that when you change the EE in the bundle manifest editor, you must also update the classpath for the project using the link below the EE section. If you don't, then you will have an EE listed first in the manifest (e.g. Foundation 1.1) but PDE will be using a different one to compile the project in your workspace (e.g. 1.4) and when a new VM (e.g. Foundation 1.1) is added to the builder, then the build will fail because you may be referencing methods not found in those libraries. I have updated the p2 bundles to have matching manifests and classpath files. Thanks. [EMAIL PROTECTED] wrote on 02/21/2008 03:47:04 PM: I have released a change to the manifest file for the org.eclipse.equinox.p2.artifact.repository project so Kim can test the Foundation EE in the build. If you have this project (and this change) loaded into your workspace and a Foundation 1.1 VM set up, it will also require that you have a project like Xerces also in your workspace. Xerces is already in the project set file so you should be good, but I just wanted to give you a heads up in case you see strange errors about not finding XML classes. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] manifest changes
When I picked up this change on two different systems, I receive build errors on the artifact repository about not being able to find the various XML files. I do have xerces in my workspace and doing the normal tricks to get the project building seem to be failing. Any suggestions on why this change would break compilation? Thanks, Tim On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote: I have released a change to the manifest file for the org.eclipse.equinox.p2.artifact.repository project so Kim can test the Foundation EE in the build. If you have this project (and this change) loaded into your workspace and a Foundation 1.1 VM set up, it will also require that you have a project like Xerces also in your workspace. Xerces is already in the project set file so you should be good, but I just wanted to give you a heads up in case you see strange errors about not finding XML classes. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
RE: [equinox-dev] [prov] manifest changes
Feels like a missing Update classpath or some such. This all works fine for me though I do have foundation 1.1 installed. Jeff -Original Message- From: [EMAIL PROTECTED] [mailto:equinox-dev- [EMAIL PROTECTED] On Behalf Of Timothy Webb Sent: Thursday, February 21, 2008 6:07 PM To: Equinox development mailing list Subject: Re: [equinox-dev] [prov] manifest changes The errors I receive are all due to is not accessible due to restriction on required library jre..\lib\rt.jar. It appears that PDE is still attempting to include those values from my JRE. My guess would be that since I don't have a foundation 1.1 compatible JVM installed, it is continuing to try and resolve the classes from the 1.6 JRE that I have configured for this workspace instead of using the org.apache.xerces project that is available. I do indeed see org.apache.xerces listed in the Plug-in Dependencies for this project. As a complete guess, I modified by hand the .classpath file. I moved the Plug-in Dependencies library prior to the JRE one. Doing this fixed the compile errors for me. I'm guessing we probably shouldn't be dependent on the ordering of the build path for something like this...? On Feb 21, 2008, at 4:44 PM, DJ Houghton wrote: This is strange... I'm not sure why you would get errors. What type of errors do you see? Are they to the effect of ...can't see due to access restriction on org.apache.xerces? Either way, the code has been checked out for the test build so I have reverted the change in HEAD so if you reload you should be ok. But we still need to figure out why you are getting these errors. [EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM: When I picked up this change on two different systems, I receive build errors on the artifact repository about not being able to find the various XML files. I do have xerces in my workspace and doing the normal tricks to get the project building seem to be failing. Any suggestions on why this change would break compilation? Thanks, Tim On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote: I have released a change to the manifest file for the org.eclipse.equinox.p2.artifact.repository project so Kim can test the Foundation EE in the build. If you have this project (and this change) loaded into your workspace and a Foundation 1.1 VM set up, it will also require that you have a project like Xerces also in your workspace. Xerces is already in the project set file so you should be good, but I just wanted to give you a heads up in case you see strange errors about not finding XML classes. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] manifest changes
My thought too. Unfortunately PDE Update Classpath didn't seem to help. On Feb 21, 2008, at 7:15 PM, Jeff McAffer wrote: Feels like a missing Update classpath or some such. This all works fine for me though I do have foundation 1.1 installed. Jeff -Original Message- From: [EMAIL PROTECTED] [mailto:equinox-dev- [EMAIL PROTECTED] On Behalf Of Timothy Webb Sent: Thursday, February 21, 2008 6:07 PM To: Equinox development mailing list Subject: Re: [equinox-dev] [prov] manifest changes The errors I receive are all due to is not accessible due to restriction on required library jre..\lib\rt.jar. It appears that PDE is still attempting to include those values from my JRE. My guess would be that since I don't have a foundation 1.1 compatible JVM installed, it is continuing to try and resolve the classes from the 1.6 JRE that I have configured for this workspace instead of using the org.apache.xerces project that is available. I do indeed see org.apache.xerces listed in the Plug-in Dependencies for this project. As a complete guess, I modified by hand the .classpath file. I moved the Plug-in Dependencies library prior to the JRE one. Doing this fixed the compile errors for me. I'm guessing we probably shouldn't be dependent on the ordering of the build path for something like this...? On Feb 21, 2008, at 4:44 PM, DJ Houghton wrote: This is strange... I'm not sure why you would get errors. What type of errors do you see? Are they to the effect of ...can't see due to access restriction on org.apache.xerces? Either way, the code has been checked out for the test build so I have reverted the change in HEAD so if you reload you should be ok. But we still need to figure out why you are getting these errors. [EMAIL PROTECTED] wrote on 02/21/2008 04:28:19 PM: When I picked up this change on two different systems, I receive build errors on the artifact repository about not being able to find the various XML files. I do have xerces in my workspace and doing the normal tricks to get the project building seem to be failing. Any suggestions on why this change would break compilation? Thanks, Tim On Feb 21, 2008, at 2:47 PM, DJ Houghton wrote: I have released a change to the manifest file for the org.eclipse.equinox.p2.artifact.repository project so Kim can test the Foundation EE in the build. If you have this project (and this change) loaded into your workspace and a Foundation 1.1 VM set up, it will also require that you have a project like Xerces also in your workspace. Xerces is already in the project set file so you should be good, but I just wanted to give you a heads up in case you see strange errors about not finding XML classes. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
