You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Jencks (JIRA)" <ji...@codehaus.org> on 2009/05/28 00:34:42 UTC
[jira] Commented: (MSHADE-51) shade plugin relocate does not play
well with maven-bundle-plugin
[ http://jira.codehaus.org/browse/MSHADE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178309#action_178309 ]
David Jencks commented on MSHADE-51:
------------------------------------
Also reported as https://issues.apache.org/jira/browse/FELIX-1184
> shade plugin relocate does not play well with maven-bundle-plugin
> -----------------------------------------------------------------
>
> Key: MSHADE-51
> URL: http://jira.codehaus.org/browse/MSHADE-51
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: David Jencks
>
> maven-bundle-plugin (from felix) v. 2.0.0
> If your build runs shade to relocate some classes from a preexisting jar and the maven-bundle-plugin to geinerate osgi metadata the bundle plugin refuses to generate any Export-Package, Import-Package or Private-Package headers. I assume it doesn't find any classes.
> I don't know whose fault this is.
> To see this in action check out https://svn.apache.org/repos/asf/geronimo/xbean/trunk/xbean-asm-shaded rev 778992 and uncomment the bundle plugin and comment the transformers section of the shade plugin config.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira