You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jesse Glick (Created) (JIRA)" <ji...@apache.org> on 2012/04/02 20:33:23 UTC

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

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


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

        

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

Posted by "Richard S. Hall (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

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

Posted by "Jesse Glick (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247389#comment-13247389 ] 

Jesse Glick commented on FELIX-3419:
------------------------------------

Note that due to FELIX-3058 the sources JAR is not built at all unless you update the bundle plugin.

I have not found a way to configure source:jar to include dependencies. I am considering whether it is necessary; I filed https://netbeans.org/bugzilla/show_bug.cgi?id=210785 for the NetBeans IDE at least to figure out on its own where to get sources for the framework classes.
                
> 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