[
https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917621#comment-13917621
]
Matt Sicker commented on LOG4J2-346:
------------------------------------
Shouldn't the module names match the artefact names in some way? Like for
instance, log4j-core-osgi-jpa should be in a directory called
log4j-core-osgi-jpa. I'm not positive on that, but it seems to be common Maven
practice to do so. At least that's what I could grok from the maven site plugin
bug MSITE-695 mentioned in the root pom.
Also, I'd prefer to use the name "bundle" over "osgi". I would think that
including "osgi" in the name indicates specific OSGi framework things like
implementations of core or compendium OSGi services, etc. Then you'd get a name
like log4j-bundle-core-jpa which kind of looks weird. I'd prefer
log4j-core-jpa-bundle. This way, all the normal JARs have corresponding
*-bundle JARs as well.
> Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding <-> slf4j-api
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-346
> URL: https://issues.apache.org/jira/browse/LOG4J2-346
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, SLF4J Bridge
> Affects Versions: 2.0-beta4, 2.0-beta8, 2.0-beta9
> Environment: OSGi R5 / Apache Felix 4.x
> Reporter: Roland Weiglhofer
> Priority: Blocker
> Labels: Bundle, OSGi, SLF4J
> Fix For: 2.0-rc2
>
> Attachments: 0001-Add-SLF4J-related-bundles.patch,
> log4j2-slf4j-impl.patch
>
>
> The bundle "Apache Log4j SLF4J Binding" (2.0.0.beta8) has an unresolved
> dependency to the package org.slf4j which is exported by the slf4j-api
> bundle. The Slf4j-api bundle has also an unresolved dependency to the package
> org.slf4j.impl which is exported by the bundle "Apache Log4j SLF4J Binding".
> Without the slf4j-api everything works. But the Slf4j-api bundle is needed
> because of given dependencies of third-party-bundles. The "Apache Log4j SLF4J
> Binding" bundle should also export the package org.slf4j.
> ----------------------------------------------------------------
> ID|State |Level|Name
> 0|Active | 0|System Bundle (4.2.1)
> 4|Active | 2|Apache Felix Bundle Repository (1.6.6)
> 5|Active | 2|Apache Felix Configuration Admin Service (1.6.0)
> 6|Active | 2|Apache Felix Gogo Command (0.12.0)
> 7|Active | 2|Apache Felix Gogo Runtime (0.10.0)
> 8|Active | 2|Apache Felix Gogo Shell (0.10.0)
> 9|Resolved | 2|Apache Felix Security Provider (2.2.0)
> 10|Active | 2|Apache Felix Shell Service (1.4.3)
> 11|Installed | 2|Apache Log4j 1.x Compatibility API (2.0.0.beta8)
> 12|Active | 2|Apache Log4j API (2.0.0.beta8)
> 13|Installed | 2|Apache Log4j Commons Logging Bridge (2.0.0.beta8)
> 14|Installed | 2|Apache Log4j Core (2.0.0.beta8)
> 15|Installed | 2|Apache Log4j SLF4J Binding (2.0.0.beta8)
> 16|Active | 2|cal10n-api (0.7.4)
> 17|Active | 2|Commons IO (2.4.0)
> 18|Active | 2|Commons Lang (2.6.0)
> 19|Active | 2|Data mapper for Jackson JSON processor (1.9.13)
> 20|Active | 2|Jackson JSON processor (1.9.13)
> 21|Active | 2|JSON.simple (1.1.1)
> 22|Installed | 2|slf4j-api (1.5.11)
> 23|Installed | 2|slf4j-ext (1.5.11)
> Unresolved constraint in bundle org.apache.logging.log4j-slf4j-impl [15]:
> Unable to resolve 15.0: missing requirement [15.0] osgi.wiring.package;
> (osgi.wiring.package=org.slf4j) [caused by: Unable to resolve 22.0: missing
> requirement [22.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.slf4j.impl)(version>=1.5.5))]
> Unresolved constraint in bundle slf4j.api [22]: Unable to resolve 22.0:
> missing requirement [22.0] osgi.wiring.package;
> (&(osgi.wiring.package=org.slf4j.impl)(version>=1.5.5))
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
