Bug 749833 - Log4j does not resolve correctly for pdebuild
Summary: Log4j does not resolve correctly for pdebuild
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: log4j
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislav Ochotnicky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 749673
TreeView+ depends on / blocked
 
Reported: 2011-10-28 16:35 UTC by Andrew Robinson
Modified: 2012-06-13 13:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-13 13:00:10 UTC
Type: ---


Attachments (Terms of Use)

Description Andrew Robinson 2011-10-28 16:35:01 UTC
Description of problem:
In the current log4j package com.sun.jdmk.comm is occurs twice in the import-package portion of the manifest of log4j.jar. This causes linking as an orbit dependency for pdebuild to fail.

Comment 1 Alexander Kurtakov 2011-11-09 20:12:30 UTC
Please test http://koji.fedoraproject.org/koji/buildinfo?buildID=271248

Comment 2 Andrew Robinson 2011-11-09 22:01:12 UTC
Pdebuild still does not resolve log4j as an orbit dependency with error:

[eclipse.buildScript] Bundle log4j:
[eclipse.buildScript]   Unsatisfied import package com.ibm.uvm.tools_0.0.0.
[eclipse.buildScript]   Unsatisfied import package com.sun.jdmk.comm_0.0.0.
[eclipse.buildScript]   Unsatisfied import package javax.jmdns_0.0.0.
[eclipse.buildScript]   Unsatisfied import package javax.jms_1.1.0.
[eclipse.buildScript]   Unsatisfied import package javax.mail_0.0.0.
[eclipse.buildScript]   Unsatisfied import package javax.mail.internet_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.config_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.helpers_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.jdbc_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.jmx_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.net_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.nt_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.or_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.or.jms_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.or.sax_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.pattern_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.spi_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.varia_0.0.0.
[eclipse.buildScript]   Unsatisfied import package org.apache.log4j.xml_0.0.0.

Related SRPM:
http://arobinso.fedorapeople.org/eclipse-mylyn-reviews-3.6.2-1.fc17.src.rpm

Comment 3 Stanislav Ochotnicky 2012-06-05 14:47:01 UTC
Can you retry with latest rawhide build? I've tried to build linked srpm and log4j errors seemed to go away. There were other issues though

Comment 4 Krzysztof Daniel 2012-06-11 09:21:17 UTC
The manifest should not contain the "uses" clause for the packages that are present in the log4j bundle. This should solve the majority of problems with unsatisfied org.apache* imports. All other imports should be satisfied by linking required jars into the pdebuild.

Comment 5 Alexander Kurtakov 2012-06-13 11:59:47 UTC
Andrew, does it work now ?
Stano, having uses is really bad when one has dynamic collection of jars, assuming it's maven-bundle-plugin that genereates the manifest it should be a matter of adding <_nouses>true</_nouses> in its configurations section.

Comment 6 Andrew Robinson 2012-06-13 13:00:10 UTC
This issue no longer affects building eclipse-mylyn-reviews.


Note You need to log in before you can comment on or make changes to this bug.