logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-345) logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.
Date Fri, 23 Aug 2013 15:47:51 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748647#comment-13748647
] 

Ralph Goers edited comment on LOG4J2-345 at 8/23/13 3:47 PM:
-------------------------------------------------------------

Is the patch file that is attached the same as what you have above? I would prefer patch files
rather than trying to cut and paste from Jira. Did you provide a way to for the build to verify
that this is working properly? For example, an OSGi based unit test that performs a bit of
logging?

I do want to apply these patches before the next release so we will get to them as soon as
we can.  
                
      was (Author: ralph.goers@dslextreme.com):
    Is the patch file that is attached the same as what you have above? I would prefer patch
files rather than trying to cut and paste from Jira. Did you provide a way to for the build
to verify that this is working properly?

I do want to apply these patches before the next release so we will get to them as soon as
we can.  
                  
> logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be
resolved.
> ----------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-345
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-345
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: log4j 1.2 emulation
>    Affects Versions: 2.0-beta4, 2.0-beta8, 2.0-beta9
>         Environment: OSGi / Apache Felix 4.x
>            Reporter: Roland Weiglhofer
>              Labels: Bundle, Export-Package, Log4j-1.2, Maven-Bundle-Plugin, OSGi, POM
>             Fix For: 2.0-beta9, 2.0
>
>         Attachments: log4j2 1.2api.patch
>
>
> 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 resolve 21.0: missing requirement
[21.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.log4j)(version>=1.2.0)(!(version>=2.0.0)))
> so...I checked the capabilities of the log4j-1.2-api bundle:
> g! inspect cap * 11
> org.apache.logging.log4j-1.2-api [11] provides:
> -----------------------------------------------
> osgi.wiring.bundle; org.apache.logging.log4j-1.2-api 2.0.0.beta8 [UNUSED]
> osgi.wiring.host; org.apache.logging.log4j-1.2-api 2.0.0.beta8 [UNUSED]
> As you can see logging.log4j-1.2-api doesn't export the log4j API 1.2. It still requires
log4j 1.2. All dependent bundles can not be resolved until I add the old log4j.jar.
> The maven-bundle-plugin does not export the packages.
> Roland 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message