You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2015/12/17 19:50:46 UTC

[jira] [Created] (SM-2777) jboss-logging 3.3.0.Final with log4j dependency 'optionalized' effectively

Benson Margulies created SM-2777:
------------------------------------

             Summary: jboss-logging 3.3.0.Final with log4j dependency 'optionalized' effectively
                 Key: SM-2777
                 URL: https://issues.apache.org/jira/browse/SM-2777
             Project: ServiceMix
          Issue Type: Improvement
            Reporter: Benson Margulies


The official Hibernate-Validator 5.2.2_Final works fine, with no need for a servicemix bundle, except that it depends on jboss-logging 3.3.0.Final.

And then one gets the following when not using log4j2:

{noformat}
org.osgi.framework.BundleException: Unable to resolve org.jboss.logging.jboss-logging [14](R 14.0): missing requirement [org.jboss.logging.jboss-logging [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.logging.log4j.message)(version>=2.0.0)(!(version>=3.0.0))) Unresolved requirements: [[org.jboss.logging.jboss-logging [14](R 14.0)] osgi.wiring.package; (&(osgi.wiring.package=org.apache.logging.log4j.message)(version>=2.0.0)(!(version>=3.0.0)))]
{noformat}

The manifest for this bundle marks all the log4j2 dependencies as optional, so why does this error even happen?

{noformat}
Import-Package: org.apache.log4j;resolution:=optional,org.apache.loggi
 ng.log4j;version="[2.0,3)";resolution:=optional,org.apache.logging.lo
 g4j.message;version="[2.0,3)";resolution:=optional,org.apache.logging
 .log4j.spi;version="[2.0,3)";resolution:=optional,org.jboss.logmanage
 r;version="[1.5,2)";resolution:=optional,org.slf4j;version="[1.7,2)";
 resolution:=optional,org.slf4j.spi;version="[1.7,2)";resolution:=opti
 onal
{noformat}

I'm writing this JIRA on the assumption that there's some way to make an SM bundle that avoids this problem. I could be wrong.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)