Hi,
you can find the patch here:
https://issues.apache.org/jira/secure/attachment/12599132/log4j2%201.2api.patch
Thx
Roland
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/log4j-1-2-api-unresolved-package-org-apache-log4j-tp39509p39993.html
Sent from the Log4j -
I tested version 2.0 beta 9 (trunk) but the error is still there. Either the
documentation should be changed or the packages of common-logging-api should
be exported.
...
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
sorry, the last post belongs to a other issue of log4j-jcl but it is
similary. The log4j 1.2 api can not be resolved. Again, the documentation is
wrong or the api has to be included in the export.
This is the right pom-configuration
properties
Can you attach patches to Jira issues?
Ralph
On Aug 20, 2013, at 5:32 AM, Roland wrote:
sorry, the last post belongs to a other issue of log4j-jcl but it is
similary. The log4j 1.2 api can not be resolved. Again, the documentation is
wrong or the api has to be included in the export.
https://issues.apache.org/jira/browse/LOG4J2-345
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/log4j-1-2-api-unresolved-package-org-apache-log4j-tp39509p39556.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
Can it be that the issue also affects other projects like log4j-to-slf4j? I
recommend to test the jars/bundles in a osgi-environment. There exists a
maven plugin for testing which includes a osgi-container.
plugin
groupIdorg.apache.felix/groupId
Hi all Log4j/OSGi experts!
Yesterday I started to migrate from log4j to log4j2. I replaced all Log4j
1.x bundles with log4j-1.2-api as described here:
http://logging.apache.org/log4j/2.x/log4j-1.2-api/index.html
But I got following error:
Unresolved constraint in bundle MyBundle [21]: Unable to
Please file a Jira. If you could supply a patch that would be great as we are
short on OSGi expertise here.
Ralph
On Aug 9, 2013, at 6:41 AM, Roland wrote:
Hi all Log4j/OSGi experts!
Yesterday I started to migrate from log4j to log4j2. I replaced all Log4j
1.x bundles with log4j-1.2-api