You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Hüseyin Kartal (JIRA)" <ji...@apache.org> on 2016/06/24 10:58:16 UTC

[jira] [Commented] (FELIX-3419) Bad aggregation of org.apache.felix.framework into org.apache.felix.main

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

Hüseyin Kartal commented on FELIX-3419:
---------------------------------------

What about just removing the dependency to org.apache.felix.framework from the org.apache.felix.main bundle since it already aggregates the framework.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)