You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/11/23 13:47:39 UTC
[jira] Updated: (JCR-2401) OSGi bundle symbolic names changed due
to changes in maven-bundle-plugin
[ https://issues.apache.org/jira/browse/JCR-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated JCR-2401:
-------------------------------------
Attachment: JCR-2401.patch
> 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
> Priority: Minor
> 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.