felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-543) add switch to prevent classifier being appended to Bundle-Version
Date Fri, 25 Apr 2008 08:03:55 GMT

     [ https://issues.apache.org/jira/browse/FELIX-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stuart McCulloch updated FELIX-543:

        Fix Version/s: maven-bundle-plugin-1.4.1
    Affects Version/s: maven-bundle-plugin-1.4.0

> add switch to prevent classifier being appended to Bundle-Version
> -----------------------------------------------------------------
>                 Key: FELIX-543
>                 URL: https://issues.apache.org/jira/browse/FELIX-543
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-1.4.0
>            Reporter: Derek Baum
>            Assignee: Stuart McCulloch
>            Priority: Minor
>             Fix For: maven-bundle-plugin-1.4.1
> I have a use-case for using classifier to create multiple bundles with different symbolic
names but the same Bundle-Version.
> This is not currently possible, as the maven-bundle-plugin automatically appends the
classifier to the Bundle-Version.
> Could some switch be added, to disable the appending of classifier to Bundle-Version?
> Thanks,
> Derek
> stuart.mcculloch wrote:
> the use-case for adding this feature was for people who
> wanted to produce JDK5 and JDK1.4 versions of the _same_ bundle, so
> because the symbolic name would be the same, the classifier must then
> be added to the version to distinguish them.
> it is the intended behaviour for the above use-case, but we could add a switch
> to turn it off - it's difficult to detect whether the classifier should be added to the
> version automatically, because each bundling process is run in isolation
> there's also no way to distinguish where the bundle version came from in Maven
> (ie. general config or specific to the classifier) once it reaches the bundleplugin,
> so a new switch is the only safe way to detect the different use-case...

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

View raw message