[JENA-1898] Force commons-codec dependency to be Jena parent POM choice

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Jena 3.15.0
• Fix Version/s: Jena 3.16.0
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 17/May/20 09:35
• Updated: 10/Nov/20 14:02
• Resolved: 17/May/20 17:41

Description

I have a project where the dependency resolution causes the commons-codec from Apache httpcomponents to be chosen (v1.11), not the version needed by Jena (v1.14).

Maven dependency rules: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

The project depends on several Jena artifacts and the encounter order of dependencies can matter.

This happens with maven 3.6.3, which is current latest.

Clearing up the projects dependencies will also fix the problem but leaves it to the user to deal with it. (The project is an old and messy scratch working area and the POM isn't neat and tidy. It was bringing in Jena test code.)

To be safe, this ticket is to force the dependency resolution by excluding common-codec from the org.apache.httpcomponents (httpclient and httpclient).

Then at least the order of any Jena artifacts does not impact the outcome.

 

Issue Links

• is duplicated by: JENA-1925 missing dependency to commons-codec in jena-arq pom