[FELIX-912] Improve default Export-Package / Private-Package settings by scanning the project source

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: maven-bundle-plugin-2.0.0
• Component/s: Maven Bundle Plugin
• Assignee: Stuart McCulloch
• Reporter: Stuart McCulloch
• Created: 30/Jan/09 16:53
• Updated: 12/Mar/09 08:05
• Resolved: 16/Feb/09 09:45

Description

The current bundleplugin default for Export-Package is based on the bundle symbolic name, which in turn is based on the Maven groupId and artifactId. While this works for a lot of projects that use the primary package as the bundle symbolic name (or for the Maven metadata) it isn't perfect. I'm thinking of enhancing the bundleplugin to look at the project source to find the main packages in the project, which could be used as the default Export-Package (or possibly Private-Package too).

The overall goal is to allow people to take a Maven project, change the packaging from "jar" to "bundle" and they'll get the same content. At the moment, because the bundle content is derived from the Export-Package / Private-Package / Include-Resource instructions this may not be the case. We already do this sort of thing for Maven resources -> Include-Resource, so there is a precedent...