[GRADLE-3087] JAR URL in Ivy repository pattern not possible Created: 13/May/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

With Ivy I was able to define an artifact pattern like "jar:[1]http://downloads.sourceforge.net/proj..." which worked pretty fine.
If I try to configure this within Gradle, it tells me that only file:, http: and https: are allowed.
Of course I can use

repositories {
add(new org.apache.ivy.plugins.resolver.URLResolver()) {
addArtifactPattern "jar:http://downloads.sourceforge.net/project/saxon/Saxon-B/[revision]/saxonb8-9-0-4j.zip!/[artifact].[ext]"
}
}

But this is deprecated and will not work anymore with 2.0 if you really remove the ability to define own repositories.
Even if not, this will constantly nag with deprecated message and as far as I can see there is currently no replacement.

Is there any reason that the URLs are restricted to file:, http: and https:?
----------------------------------------------------------------------------------------
[1] http://downloads.sourceforge.net/project/saxon/Saxon-B/[revision]/saxonb8-9-0-4j.zip!/[artifact].[ext]

 Comments   
Comment by Gradle Forums [ 13/May/14 ]

Probably these are the only URL types that are implemented.

Comment by Gradle Forums [ 13/May/14 ]

Ah, ok, I thought you are still using Ivy under the hood, especially as it works fine with the Ivy resolver.
May I ask for JAR URL support then?

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:39:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.