[GRADLE-2179] Url-based dependencies Created: 17/Mar/12  Updated: 29/Nov/16  Resolved: 29/Nov/16

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

Type: New Feature
Reporter: Yennick Trevels Assignee: Unassigned
Resolution: Won't Fix Votes: 3


 Description   

For my plugin I want to specify dependencies as a url. Something like this:

dependencies

{ sdk name: 'flex-sdk', version: 4.6, ext: 'zip', url: 'http://fpdownload.adobe.com/pub/flex/sdk/builds/flex4.6/flex_sdk_4.6.0.23201B.zip' }

I'm the project lead of the GradleFx plugin and I would like to support this so that users can specify the Flex SDK as a dependency (right now they have to download it themselves).
If Gradle would support this and cache the file, GradleFx can unzip it to a GradleFx specific folder. In my opinion this is the cleanest solution because in the end the Flex SDK is a dependency and the users have a variety of ways to specify the SDK dependency (url-based, maven-based or ivy-based when the zip is uploaded to such a repository).

And maybe the Java plugin for Gradle could then use the same mechanism for the Java SDK, which would reduce the required setup when running a java build.

 Comments   
Comment by Yennick Trevels [ 20/Sep/12 ]

I found a workaround for this (in case someone should need this right now), but a cleaner solution for this would be great.

repositories {
add(new org.apache.ivy.plugins.resolver.URLResolver())

{ name = 'Apache' addArtifactPattern 'http://apache.cu.be/incubator/flex/4.8.0-incubating/binaries/[module]-[revision]-incubating-bin.[ext]' }

}

dependencies

{ merged group: 'org.apache', name: 'apache-flex-sdk', version: '4.8.0', ext: 'zip' }
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 Yennick Trevels [ 29/Nov/16 ]

This issue can be closed since there's now a clean way to get this working.

Comment by Benjamin Muschko [ 29/Nov/16 ]

Closing as requested.

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