Bug 1401053 - Consider moving wsdl4j to rh-java-common
Summary: Consider moving wsdl4j to rh-java-common
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-java-common
Version: rh-java-common
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 2.4
Assignee: Michael Simacek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 16:12 UTC by Mat Booth
Modified: 2017-01-11 13:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 10:02:50 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mat Booth 2016-12-02 16:12:16 UTC 
Description of problem:

Currently, "wsdl4j" exists in both rh-maven33 and rh-eclipse46 collections -- consider moving it to shared collection rh-java-common to reduce maintenance overhead.
Comment 1 Michael Simacek 2017-01-10 14:26:03 UTC 
rh-maven33-wsdl4j is not required by anything, it seems to be there as a legacy from maven30. maven30-wsdl4j is required only for building rh-java-common-tomcat. tomcat doesn't actually reference wsdl4j in the code, and the package builds fine with it removed. It doesn't have runtime Requires on it either.

So I think that in order to reduce maintenance, it would be better to keep wsdl4j only in rh-eclipse46 and drop it from rh-maven33.
Comment 3 RHEL Program Management 2017-01-11 10:02:50 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.