Qpid has introduced a new class to the standard package log4j.xml (yes they should not have done that). Since we can not export a given package from two different OSGi bundle, the solution has been to have it exported from the logging bundle.
Thanks, Danushka On Tue, Jan 18, 2011 at 11:25 AM, Sumedha Rubasinghe <sume...@wso2.com>wrote: > Why are we having a dependency to qpid-broker from logging component? > > /sumedha > > Missing: > ---------- > 1) org.apache.qpid:qpid-broker:jar:0.9-wso2v1 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.qpid > -DartifactId=qpid-broker -Dversion=0.9-wso2v1 -Dpackaging=jar > -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.apache.qpid > -DartifactId=qpid-broker -Dversion=0.9-wso2v1 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wso2.governance:wso2greg:jar:3.6.0-SNAPSHOT > 2) > org.wso2.carbon:org.wso2.carbon.registry.ws.client:jar:3.1.0-SNAPSHOT > 3) org.wso2.carbon:org.wso2.carbon.logging:jar:3.1.0-SNAPSHOT > 4) org.apache.qpid:qpid-broker:jar:0.9-wso2v1 > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
