Community
Participate
Working Groups
Build Identifier: M20100211-1343 I tried to export some libs (springframekork) into an local p2 repository. I created a target platform and a feature project. Exporting this feature ends up in an error, that some dependencies could not be resolved. I looked at it and found, that all of them are optional dependencies. I also found a workaround for that error: When the org.eclipse.osgi.jar bundle is included in the current target platform, the feature export is working fine. But I think that this would be a bug. Why is the org.eclipse.osgi.jar bundle needed? Reproducible: Always Steps to Reproduce: I added a sample project. 1. import the bugreport project into the workspace 2. set the target platform with the contained target.target file 3. open the feature.xml and choose "export a deployable feature" with "Generate metadata repository" enabled This should throw the reported error. To prevent the error, just add the org.eclipse.osgi_3.6.0.v20100301.jar to the "libs" folder and refresh the target platform. Now the export works fine
Created attachment 165894 [details] example project
The source of the resolution problems for org.springframework.jdbc is javax.sql and javax.sql.rowset. These two packages are not marked optional. When org.eclipse.osgi is in the target, it will export the system bundles, if you haven't defined any EEs for your build, it would export 1.6 or 1.7 I think, which does include those packages. The error message does display the full list of unsatisfied imports even though most of them are optional. We should probably only show the non-optional imports. In the UI, it is easier to see the problem by looking at the "Target Platform State" view.
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
