Bug 530373 - Move from Require-Bundle to Import-Package
Summary: Move from Require-Bundle to Import-Package
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 5.1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Next   Edit
Assignee: Pierre-Charles David CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-01-26 07:57 EST by Pierre-Charles David CLA
Modified: 2018-08-27 11:27 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Charles David CLA 2018-01-26 07:57:37 EST 
Beside being cleaner, this would probably help in restructuring Sirius itself in the future, by allowing moving packages in different bundles.

The change should concern both internal dependencies between Sirius bundles and from Sirius to other projects. Note that some projects do not version their packages (e.g. SWT) so applying this rule to them would create a lot of warnings for un-versioned dependencies. Either we should propose the projects in question to add versions to their packages, or we should stick to Require-Bundle for them, as long as they represent the exception and are stable projects.
Comment 1 Pierre-Charles David CLA 2018-04-03 11:17:34 EDT 
I could not find an automated procedure to do this, so it would be rather costly. In addition, there is a risk that the way we manage version numbers in packages would expose us to potential issues. Maybe we can start with some non-critical plug-ins in 6.0 to gain some experience and see if it's worth the effort.