You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stuart McCulloch (JIRA)" <ji...@apache.org> on 2009/01/30 17:54:59 UTC

[jira] Created: (FELIX-912) Improve default Export-Package / Private-Package settings by scanning the project source

Improve default Export-Package / Private-Package settings by scanning the project source
----------------------------------------------------------------------------------------

                 Key: FELIX-912
                 URL: https://issues.apache.org/jira/browse/FELIX-912
             Project: Felix
          Issue Type: New Feature
          Components: Maven Bundle Plugin
            Reporter: Stuart McCulloch
            Assignee: Stuart McCulloch
            Priority: Minor
             Fix For: maven-bundle-plugin-1.6.0


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...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Work started: (FELIX-912) Improve default Export-Package / Private-Package settings by scanning the project source

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on FELIX-912 started by Stuart McCulloch.

> Improve default Export-Package / Private-Package settings by scanning the project source
> ----------------------------------------------------------------------------------------
>
>                 Key: FELIX-912
>                 URL: https://issues.apache.org/jira/browse/FELIX-912
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>            Reporter: Stuart McCulloch
>            Assignee: Stuart McCulloch
>            Priority: Minor
>             Fix For: maven-bundle-plugin-2.0.0
>
>
> 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...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (FELIX-912) Improve default Export-Package / Private-Package settings by scanning the project source

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart McCulloch resolved FELIX-912.
------------------------------------

    Resolution: Fixed

We now base the default Export-Package on the local source files, which makes it much easier to migrate existing Maven projects to OSGi.

> Improve default Export-Package / Private-Package settings by scanning the project source
> ----------------------------------------------------------------------------------------
>
>                 Key: FELIX-912
>                 URL: https://issues.apache.org/jira/browse/FELIX-912
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>            Reporter: Stuart McCulloch
>            Assignee: Stuart McCulloch
>            Priority: Minor
>             Fix For: maven-bundle-plugin-2.0.0
>
>
> 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...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.