Re: ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger
http://apache-logging.6191.n7.nabble.com/Discussion-about-correct-initialization-of-log4j2-in-OSGi-context-td39733.html -- View this message in context: http://apache-logging.6191.n7.nabble.com/ERROR-StatusLogger-Unable-to-locate-a-logging-implementation-using-SimpleLogger-tp39952p39955.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: log4j-1.2-api -> unresolved package org.apache.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.
...
org.apache.felix
maven-bundle-plugin
true
true
${osgi.symbolicName}
${osgi.import}
${osgi.export}
${project.url}
commons-logging-api;version=1.1;scope=compile|runtime;inline=false
<_exportcontents>
org.apache.commons.logging;version=1.1
...
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/log4j-1-2-api-unresolved-package-org-apache-log4j-tp39509p39967.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: log4j-1.2-api -> unresolved package org.apache.log4j
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
org.apache.log4j;version=1.2,org.apache.log4j.helpers;version=1.2,org.apache.log4j.config;version=1.2,org.apache.log4j.spi;version=1.2,org.apache.log4j.xml;version=1.2
...
org.apache.felix
maven-bundle-plugin
true
true
...
${osgi.export.log4j1.2}
...
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/log4j-1-2-api-unresolved-package-org-apache-log4j-tp39509p39968.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
Replace commons.logging with jcl-bridge?
The doku. says: "Usage Using the Commons Logging Bridge is straightforward. Simply add the bridge jar along with the other Log4j 2 jars and all logging done using the Commons Logging API will be routed to Log4j." Should I replace the commons.logging jar with jcl-bridge or should I just add the jcl-bridge? I think it is not clearly defined in an OSGi-environment which implementation is used if both JARs are installed. So, I would say that the common.logging jar has to be replaced. This assumes that the commons.logging api is somewhere exported. But the commons.logging api as well as the commons.logging impl. are simple JARs but not bundles and they can not be installed in an OSGi-environment. I would embed and export the commons.logging api within the jcl-bridge. ... org.apache.felix maven-bundle-plugin ... commons-logging-api;version=1.1;scope=compile|runtime;inline=false <_exportcontents> org.apache.commons.logging;version=1.1 ... ... -- View this message in context: http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Replace commons.logging with jcl-bridge?
The commons-logging jar needs to be included along with the jcl-bridge. The jcl-bridge only supplies the LogFactory and Log implementations, not the API. On Aug 20, 2013, at 6:10 AM, Roland wrote: > The doku. says: > > "Usage > > Using the Commons Logging Bridge is straightforward. Simply add the bridge > jar along with the other Log4j 2 jars and all logging done using the Commons > Logging API will be routed to Log4j." > > Should I replace the commons.logging jar with jcl-bridge or should I just > add the jcl-bridge? I think it is not clearly defined in an OSGi-environment > which implementation is used if both JARs are installed. So, I would say > that the common.logging jar has to be replaced. This assumes that the > commons.logging api is somewhere exported. But the commons.logging api as > well as the commons.logging impl. are simple JARs but not bundles and they > can not be installed in an OSGi-environment. I would embed and export the > commons.logging api within the jcl-bridge. > > ... > >org.apache.felix >maven-bundle-plugin > > >... > > > commons-logging-api;version=1.1;scope=compile|runtime;inline=false > ><_exportcontents> > org.apache.commons.logging;version=1.1 > > ... > > > > ... > > > > > > -- > View this message in context: > http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970.html > Sent from the Log4j - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: log4j-1.2-api -> unresolved package org.apache.log4j
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.
>
> This is the right pom-configuration
>
>
> org.apache.log4j;version=1.2,org.apache.log4j.helpers;version=1.2,org.apache.log4j.config;version=1.2,org.apache.log4j.spi;version=1.2,org.apache.log4j.xml;version=1.2
>
> ...
>
>org.apache.felix
>maven-bundle-plugin
>true
>true
>
>
>...
>${osgi.export.log4j1.2}
>...
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-logging.6191.n7.nabble.com/log4j-1-2-api-unresolved-package-org-apache-log4j-tp39509p39968.html
> Sent from the Log4j - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Replace commons.logging with jcl-bridge?
How does log4j2-jcl ensure that OSGi-bundles get its implemention but not the commons.logging impl.? -- View this message in context: http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970p39976.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Replace commons.logging with jcl-bridge?
The log4j2-jcl jar contains a file META-INF/services/org.apache.commons.logging.LogFactory which contains org.apache.logging.log4j.jcl.LogFactoryImpl. Commons Logging uses that class name to bind the implementation to its API. Ralph On Aug 20, 2013, at 7:53 AM, Roland wrote: > How does log4j2-jcl ensure that OSGi-bundles get its implemention but not the > commons.logging impl.? > > > > -- > View this message in context: > http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970p39976.html > Sent from the Log4j - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Replace commons.logging with jcl-bridge?
Hi, OK, I've got it. Thx Roland -- View this message in context: http://apache-logging.6191.n7.nabble.com/Replace-commons-logging-with-jcl-bridge-tp39970p39990.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
