[IVY-1493] Can't resolve wildcard dependencies when remote artifact server does not set content-type header.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.0-RC1, 2.5.0-rc1
• Fix Version/s: 2.4.0
• Component/s: Core

Environment

JDK6, Artifactory 3.4.0

• Assignee: Nicolas Lalevée
• Reporter: Andrew Bernhagen
• Created: 09/Oct/14 22:07
• Updated: 26/Dec/14 20:03
• Resolved: 27/Oct/14 23:38

Description

Let's say I define an ivy dependency like this:

<dependency org="org.hibernate" name="hibernate-core" rev="4.+" conf="compile->default" />

I know this is a valid dependency for my artifact repository (tested against Artifactory 3.4.0) as it is:
1. Valid if I specify the revision as 4.3.6.Final.
2. Valid if I pull 4.+ from Maven central directly.

The reason it fails when pulling 4.+ from my private artifact repository is because Artifactory does not set the Content-Type header on certain requests. I believe this problem to be related to IVY-1400.

I was able to code a workaround as a test to see if it fixed my problem by editing org.apache.ivy.util.url.ApacheURLLister (1557968) line 113 to become:

BufferedReader r = null;
if (charset == null)

{ r = new BufferedReader(new InputStreamReader(contentStream)); }

else

{ r = new BufferedReader(new InputStreamReader(contentStream, charset)); }

This resolved the issue in my test case.

Issue Links

• is broken by: IVY-1452 NullPointerException when accessing charset to invalid URL
• is related to: IVY-1400 NullPointerException - problem while listing resources