[GRADLE-1203] renaming causes problem in native lib dependency handling Created: 03/Nov/10 Updated: 10/Feb/17 Resolved: 10/Feb/17
I was recently bitten by a lib dependency feature of gradle(Ivy?).
The 3rd party libs my project is depended on are stored in an own repo.
This can be a problem with jars containg Class-Path manifest info, too.
|Comment by Russ Egan [ 04/Jan/11 ]
Are there any workarounds for this issue? I'm running into the same thing, with a dll dependency. And I think we're going to have zip and tar dependencies we'll run into this with too.
|Comment by Russ Egan [ 05/Jan/11 ]
Found a workaround from Hans, here: http://stackoverflow.com/questions/3250668/in-gradle-how-do-ignore-the-cache-for-a-local-ivy-repository
This worked for me:
|Comment by Zsolt Kúti [ 05/Jan/11 ]
Thanks for the info! I'll check it.
|Comment by Russ Egan [ 27/Jan/11 ]
While this was working for me, I decided to go a different direction. I don't really care how the file is named in ivy's cache. I only care about their name when I copy them into my distribution archives. So I'm just renaming them during the copy. Then I don't need to modify the structure of my repository for it. And it's way fewer lines in my build file.
|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:
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.