felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Topping (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3472) Source inclusion for targets of <Embed-Dependency>
Date Mon, 23 Apr 2012 13:17:34 GMT

    [ https://issues.apache.org/jira/browse/FELIX-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259591#comment-13259591

Brian Topping commented on FELIX-3472:

In thinking about it, if this is going to be resolved, it's probably easiest to include the
functionality of maven-source-plugin in maven-bundle-plugin, enabled by a <configuration>
switch.  It's not a very difficult use case that will change (if ever) and far less complicated
than anything else.  I can put together a patch, just say the word.
> Source inclusion for targets of <Embed-Dependency> 
> ---------------------------------------------------
>                 Key: FELIX-3472
>                 URL: https://issues.apache.org/jira/browse/FELIX-3472
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.7
>            Reporter: Brian Topping
>            Priority: Minor
> This seems like it would be rather hideous to fix, but I didn't see it anywhere and thought
I would note it.
> When the <Embed-Dependency> instruction is used along with the maven-source-plugin,
source artifacts that otherwise exist alongside the dependency jar artifacts are not included
in the source jars of the artifact being built.  It's not difficult to manually add the source
jars for each embedded dependency on a remote project, but gets annoying when changes to the
project cause the source jar attachments to be wiped out when the project is reloaded.
> It seems like it would be difficult to fix because either maven-source-plugin needs to
know about the various locations that bundle instructions can live or bundle plugin needs
to add sources to existing source jars.  Both of of those solutions violate containment of
the other plugin's role.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message