Summary: | feature export files an error for optional dependencies | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Lars Fischer <reschifl> | ||||
Component: | Build | Assignee: | pde-build-inbox <pde-build-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | aniefer | ||||
Version: | 4.0 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | stalebug | ||||||
Attachments: |
|
Description
Lars Fischer
2010-04-23 06:47:46 EDT
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. 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. 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. |