felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3419) Bad aggregation of org.apache.felix.framework into org.apache.felix.main
Date Mon, 02 Apr 2012 18:45:25 GMT

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

Richard S. Hall commented on FELIX-3419:

If you know of some way to tell Maven to include the source of framework into the main source
JAR, then I wouldn't have a problem with it, but I prefer to keep them as separate projects
that create an aggregated JAR since that is more convenient.
> Bad aggregation of org.apache.felix.framework into org.apache.felix.main
> ------------------------------------------------------------------------
>                 Key: FELIX-3419
>                 URL: https://issues.apache.org/jira/browse/FELIX-3419
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Main
>    Affects Versions: framework-4.0.2
>            Reporter: Jesse Glick
>            Priority: Minor
>              Labels: maven
> org.apache.felix.felix-4.0.2.jar in Maven Central (org.apache.felix:org.apache.felix.main:4.0.2:jar)
aggregates classes from org.apache.felix.framework, as a convenience I suppose. But it is
not very convenient when trying to analyze stack traces, debug, etc. from Maven projects,
because while org.apache.felix:org.apache.felix.main:4.0.2:sources:jar (org.apache.felix.main-4.0.2-sources.jar)
exists, it includes just the two classes in the org.apache.felix.main package.
> Simpler and better would be to distribute felix.framework and felix.main as disjoint
artifacts, but if you do want to produce an aggregated JAR, its source artifact needs to include
matches for all the compiled classes in the JAR.

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