[KULRICE-8616] Wrong slf4j-log4j12 version resolved when depending on ricecore-impl Created: 30/Nov/12 Updated: 21/Mar/13 Resolved: 11/Dec/12
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Security Level:
Closed
Kuali Rice Development
Development
2.2.0-m4, 2.2
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug Fix
Scott Gibson (Inactive)
Fixed
None
Not Specified
Similar issues:
KULRICE-8615
2.1.3
Public (Public: Anyone can view)
Priority:
Assignee:
Votes:
Major
Corey Pedersen (Inactive)
0
Not Specified
Not Specified
Wrong commons-collections version when depending
on rice-kim-api
KULRICE-244
resolve core service dependency issues
KULRICE-12312 FlexRM#resolveResponsibilityId resolves
responsibilities incorrectly
KULRICE-6353 Add explicit dependency to asm version 3.3.1 in ksbclient-impl pom
KULRICE-1760 mvn eclipse:eclipse is not pulling in dependencies
properly
KULRICE-11491 Remove duplicated test resources from KRAD web
framework
KULRICE-6967 Rice impl and krad depend on different versions of slf4j
KULRICE-1417 Add BCEL 5.1 to dependencies
KULRICE-1794 workflow depends on unauthorized jsp being in wrong
location when running with workflow web content
embedded
KULRICE-8499 Rice version is wrong in installation guide
documentation for maven archetype (section 5, maven
cli)
KAI Review
Status:
KTI Review
Status:
Not Required
Not Required
Description
If an external project depends on rice-core-impl a version of slf4j-log4j12 (1.4.2) will be
resolved that conflicts with the slf4j-api version (1.6.4). The conflicting version is coming from
the displaytag dependency. I'm not sure if the goal when using slf4j is to not include an impl for
consumers - but this can be resolved by adding an explicit dependency on the slf4j-log4j12,
excluding it from the displaytag dependency, or possibly removing the displaytag dependency
(nothing in that module stands out as requiring it, but I don't have the project open to test).
Comments
Comment by Corey Pedersen (Inactive) [ 11/Dec/12 ]
Rice 2.1 pom.xml has explicit exclusions for slf4j artifacts in its' displaytag dependency
statement. If a project declares a dependency on a rice module which has a declared dependency
for slf4j-log4j12 and for rice-core-impl module then the parent declared version of slf4j-log4j12
is loaded. If an explicit dependency for slf4j-log4j12 is not declared in any of the modules
referenced by the project then a default version(1.4.2) of slf4j-log4j12 is utilized when
referencing the rice-core-impl module.
To make the version of slf4j-log4j12 which is used by rice-core-impl consistent, I am adding a
explicit dependency to the rice-core-impl pom.xml. This will enable the existing exclusions in
the parent rice pom.xml and will utilize the version specified.
Comment by Corey Pedersen (Inactive) [ 11/Dec/12 ]
Committed revision 36198. Issue resolved.
Generated at Tue Feb 09 12:45:29 CST 2016 using JIRA 6.1.5#6160sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.