Bug 1185297 - RFE: introduce log4j-1 symlink to point to the latest log4j from 1.x line
Summary: RFE: introduce log4j-1 symlink to point to the latest log4j from 1.x line
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: log4j12
Version: 21
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1182240
TreeView+ depends on / blocked
 
Reported: 2015-01-23 12:15 UTC by Tomas Lestach
Modified: 2015-01-27 03:04 UTC (History)
3 users (show)

Fixed In Version: 1.2.17-8
Clone Of:
Environment:
Last Closed: 2015-01-26 17:28:14 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Tomas Lestach 2015-01-23 12:15:52 UTC 
Description of problem:
Please, create a (log4j-1) symlink within the log4j12 rpm that would point to the latest log4j v1 jar.


Actual results:
Current available log4j12 does not include such a symlink ...

# rpm -ql log4j12 | grep jar
/usr/share/java/log4j-1.2.17.jar
/usr/share/java/log4j12-1.2.17.jar
# rpm -q log4j12 
log4j12-1.2.17-7.fc21.noarch


Additional info:
For more information check Bug 1182346.
Comment 1 Mikolaj Izdebski 2015-01-23 14:06:18 UTC 
Fixed in log4j12-1.2.17-8
Comment 2 Fedora Update System 2015-01-23 15:03:26 UTC 
log4j12-1.2.17-8.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/log4j12-1.2.17-8.fc21
Comment 3 Mikolaj Izdebski 2015-01-24 06:14:11 UTC 
Moving to QA for testing.
Comment 4 Mikolaj Izdebski 2015-01-26 17:28:14 UTC 
I believe that this feature is included in log4j12-1.2.17-8,
which is available in updates for Fedora 21, so I am closing this bug now.

The build which includes the feature can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=605988
Comment 5 Fedora Update System 2015-01-27 03:04:16 UTC 
log4j12-1.2.17-8.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.