You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Lars Fischer <re...@googlemail.com> on 2010/07/08 13:18:29 UTC
1.2.16 with broken OSGi Import-Package?
Hello,
I would like to use log4j 1.2.16 inside an eclipse OSGi project and
tried to add the log4j-1.2.16.jar to my target platform.
But the jar is not recognized as OSGi bundle.
I discovered, that the reason is a doubled "Import-Package" entry of
"com.sun.jdmk.comm;resolution:=optional" in the MANIFEST.MF. This
prevents the jar from being loaded into the target platform. :(
I can remove one of the entries by hand. With this change the jar can
be added. But this is no good solution for me.
Could someone confirm that this is a bug in 1.2.16?
Kind regards,
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: 1.2.16 with broken OSGi Import-Package?
Posted by Curt Arnold <ca...@apache.org>.
The duplication was reported in https://issues.apache.org/bugzilla/show_bug.cgi?id=43282 and is fixed in the SVN HEAD.
On Jan 14, 2011, at 2:11 PM, Gary Gregory wrote:
> I count only on " com.sun.jdmk.comm;resolution:=optional" in:
>
> Import-Package: com.ibm.uvm.tools;resolution:=optional,com.sun.jdmk.co
> mm;resolution:=optional,com.sun.jdmk.comm;resolution:=optional,javax.
> jmdns,javax.jms;resolution:=optional,javax.mail;resolution:=optional,
> javax.mail.internet;resolution:=optional,javax.management;resolution:
> =optional,javax.naming;resolution:=optional,javax.swing;resolution:=o
> ptional,javax.swing.border;resolution:=optional,javax.swing.event;res
> olution:=optional,javax.swing.table;resolution:=optional,javax.swing.
> text;resolution:=optional,javax.swing.tree;resolution:=optional,javax
> .xml.parsers,org.apache.log4j,org.apache.log4j.config,org.apache.log4
> j.helpers,org.apache.log4j.jdbc,org.apache.log4j.jmx,org.apache.log4j
> .net,org.apache.log4j.nt,org.apache.log4j.or,org.apache.log4j.or.jms,
> org.apache.log4j.or.sax,org.apache.log4j.pattern,org.apache.log4j.spi
> ,org.apache.log4j.varia,org.apache.log4j.xml,org.w3c.dom,org.xml.sax,
> org.xml.sax.helpers
>
> Gary Gregory
> Senior Software Engineer
> Rocket Software
> 3340 Peachtree Road, Suite 820 • Atlanta, GA 30326 • USA
> Tel: +1.404.760.1560
> Email: ggregory@seagullsoftware.com
> Web: seagull.rocketsoftware.com
>
>
>
>> -----Original Message-----
>> From: Lars Fischer [mailto:reschifl@googlemail.com]
>> Sent: Thursday, July 08, 2010 07:18
>> To: log4j-user@logging.apache.org
>> Subject: 1.2.16 with broken OSGi Import-Package?
>>
>> Hello,
>>
>> I would like to use log4j 1.2.16 inside an eclipse OSGi project and
>> tried to add the log4j-1.2.16.jar to my target platform.
>> But the jar is not recognized as OSGi bundle.
>>
>> I discovered, that the reason is a doubled "Import-Package" entry of
>> "com.sun.jdmk.comm;resolution:=optional" in the MANIFEST.MF. This
>> prevents the jar from being loaded into the target platform. :(
>>
>> I can remove one of the entries by hand. With this change the jar can
>> be added. But this is no good solution for me.
>>
>> Could someone confirm that this is a bug in 1.2.16?
>>
>> Kind regards,
>> Lars
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: 1.2.16 with broken OSGi Import-Package?
Posted by Gary Gregory <GG...@seagullsoftware.com>.
I count only on " com.sun.jdmk.comm;resolution:=optional" in:
Import-Package: com.ibm.uvm.tools;resolution:=optional,com.sun.jdmk.co
mm;resolution:=optional,com.sun.jdmk.comm;resolution:=optional,javax.
jmdns,javax.jms;resolution:=optional,javax.mail;resolution:=optional,
javax.mail.internet;resolution:=optional,javax.management;resolution:
=optional,javax.naming;resolution:=optional,javax.swing;resolution:=o
ptional,javax.swing.border;resolution:=optional,javax.swing.event;res
olution:=optional,javax.swing.table;resolution:=optional,javax.swing.
text;resolution:=optional,javax.swing.tree;resolution:=optional,javax
.xml.parsers,org.apache.log4j,org.apache.log4j.config,org.apache.log4
j.helpers,org.apache.log4j.jdbc,org.apache.log4j.jmx,org.apache.log4j
.net,org.apache.log4j.nt,org.apache.log4j.or,org.apache.log4j.or.jms,
org.apache.log4j.or.sax,org.apache.log4j.pattern,org.apache.log4j.spi
,org.apache.log4j.varia,org.apache.log4j.xml,org.w3c.dom,org.xml.sax,
org.xml.sax.helpers
Gary Gregory
Senior Software Engineer
Rocket Software
3340 Peachtree Road, Suite 820 • Atlanta, GA 30326 • USA
Tel: +1.404.760.1560
Email: ggregory@seagullsoftware.com
Web: seagull.rocketsoftware.com
> -----Original Message-----
> From: Lars Fischer [mailto:reschifl@googlemail.com]
> Sent: Thursday, July 08, 2010 07:18
> To: log4j-user@logging.apache.org
> Subject: 1.2.16 with broken OSGi Import-Package?
>
> Hello,
>
> I would like to use log4j 1.2.16 inside an eclipse OSGi project and
> tried to add the log4j-1.2.16.jar to my target platform.
> But the jar is not recognized as OSGi bundle.
>
> I discovered, that the reason is a doubled "Import-Package" entry of
> "com.sun.jdmk.comm;resolution:=optional" in the MANIFEST.MF. This
> prevents the jar from being loaded into the target platform. :(
>
> I can remove one of the entries by hand. With this change the jar can
> be added. But this is no good solution for me.
>
> Could someone confirm that this is a bug in 1.2.16?
>
> Kind regards,
> Lars
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: 1.2.16 with broken OSGi Import-Package?
Posted by Curt Arnold <ca...@apache.org>.
There was a duplicated package in the import declarations which caused the manifest to be rejected. It should be fixed in the SVN HEAD.
On Jul 8, 2010, at 6:18 AM, Lars Fischer wrote:
> Hello,
>
> I would like to use log4j 1.2.16 inside an eclipse OSGi project and
> tried to add the log4j-1.2.16.jar to my target platform.
> But the jar is not recognized as OSGi bundle.
>
> I discovered, that the reason is a doubled "Import-Package" entry of
> "com.sun.jdmk.comm;resolution:=optional" in the MANIFEST.MF. This
> prevents the jar from being loaded into the target platform. :(
>
> I can remove one of the entries by hand. With this change the jar can
> be added. But this is no good solution for me.
>
> Could someone confirm that this is a bug in 1.2.16?
>
> Kind regards,
> Lars
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org