[CONTROLLER-1343] Remove Import-Package section from maven-bundle-plugin configuration Created: 28/May/15 Updated: 25/Jul/23 Resolved: 23/Jul/17 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 3401 | ||||||||
| Description |
|
The maven-bundle-plugin can generate an appropriate Import-Package section in the OSGi manifest automatically. If an Import-Package section is present then it will override the default maven-bundle-plugin behavior. As per rovarga - Import-Package is only ever needed if you consume a package which happens to have an '.impl' component in its name. As per OSGi, that implies implementation-level dependency and is discouraged. The fix is to use some creativity in naming your packages |
| Comments |
| Comment by Colin Dixon [ 16/Jun/15 ] |
|
Tony says there are 21 artifacts in the controller, that do this right now. He says that for some of them just removing it is likely to cause problems. |
| Comment by Tom Pantelis [ 05/Jul/17 ] |
