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

Posted to dev@felix.apache.org by "Steven Huypens (JIRA)" <ji...@apache.org> on 2019/03/22 17:17:00 UTC

[jira] [Created] (FELIX-6087) Add logging info when fragment bundle cannot be resolved

Steven Huypens created FELIX-6087:
-------------------------------------

             Summary: Add logging info when fragment bundle cannot be resolved
                 Key: FELIX-6087
                 URL: https://issues.apache.org/jira/browse/FELIX-6087
             Project: Felix
          Issue Type: Improvement
          Components: Framework
            Reporter: Steven Huypens


I recently tried to add the fragment bundle [groovy-json 2.5.6|https://mvnrepository.com/artifact/org.codehaus.groovy/groovy-json/2.5.6] to my Apache Felix 6.0.2 installation (alraedy containg the host), but the bundle wouldn't resolve. Even worse, I didn't find a cause in the logging which left me completely puzzled.

 

Fortunately I got some expert help telling me the fragment needed OSGi support for service loader which is provided by the [Aries SPI Fly|http://aries.apache.org/modules/spi-fly.html] project and thus one needs this bundle and the bundles providing the packages/services it depends on.

 

So my problem was solved, but I think it would be a great help if some logging would be added, explaining why the fragment cannot be resolved.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)