jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2401) OSGi bundle symbolic names changed due to changes in maven-bundle-plugin
Date Wed, 25 Nov 2009 14:13:39 GMT

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

Jukka Zitting updated JCR-2401:

       Resolution: Fixed
    Fix Version/s: 2.0-beta4
         Assignee: Jukka Zitting
           Status: Resolved  (was: Patch Available)

Patch applied in revision 884110. Thanks!

> OSGi bundle symbolic names changed due to changes in maven-bundle-plugin
> ------------------------------------------------------------------------
>                 Key: JCR-2401
>                 URL: https://issues.apache.org/jira/browse/JCR-2401
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 2.0-beta3
>            Reporter: Bertrand Delacretaz
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.0-beta4
>         Attachments: JCR-2401.patch
> See FELIX-1886 - I have noticed this with jackrabbit-jcr-commons 2.0-beta3 but I assume
all modules which use maven-bundle-plugin are affected.
> Having bundle symbolic name changes is problematic as OSGi frameworks then consider the
old a new bundles to be different components, instead of different versions of the same component.
> The simplest way to go back to the previous symbolic names is probably to use the maven-bundle-plugin
config workaround described in FELIX-1886, in the jackrabbit parent pom (or whever that plugin
is configured).
> I'll try that and supply a patch.

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

View raw message