| Summary: | Bundle export fails when 3 particular bundles are in target platform. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dimitar Giormov <dimitar.giormov> | ||||
| Component: | Build | Assignee: | pde-build-inbox <pde-build-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | curtis.windatt.public | ||||
| Version: | 3.7.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Hi we do not need solution for this problem anymore, you can close the ticket if you like. Closing at reporter's request. |
Created attachment 204311 [details] problem bundle Hi, we are trying to export a bundle that has property: Bundle-RequiredExecutionEnvironment: J2SE-1.4 the bundle has dependency to javax.xml.namespace package, which cannot be resolved. So in order to reproduce easier the problem we have created a problem.bundle that illustrates the problem. (see attachment) After some debugging and trial and error we have found the cause, but we cannot tell why this is happening. In short the target platform we use have 3 bundles that kept in one and the same target platform cause the problem. These bundles are: com.springsource.org.apache.xerces, com.springsource.org.apache.xmlcommons and org.eclipse.osgi. Note that the bundle actually depends only on one of the 3 bundles. Removing one of the other 2 bundles from the target platform fixes the problem and the deployable plugin export passes successfully. In the bundle I have placed a target file that gathers these 3 bundles. You can use it or you can also just copy these 3 bundles in a new plugins folder and create a new target. BTW: Removing the Bundle-RequiredExecutionEnvironment fixes the problem, but in our real use-case we cannot do that. best regards, Dimitar