[GRADLE-1203] renaming causes problem in native lib dependency handling Created: 03/Nov/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Zsolt Kúti Assignee: Unassigned
Resolution: Won't Fix Votes: 0


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.
One of them contains native libs. This one is shipped with artifacts (libs) not having versioning info in their names. Nevertheless, I placed them into a regular dir structure that does contain this info (e.g. org.foo/bar/x.y.z/artifact-native.dll; .../artifact.jar ... etc.).
The problem came when an other artifact (artifact.jar) of this package wanted to use this native lib, but could not find it.
It turned out artifact-native.dll has been renamed by gradle to artifact-native-x.y.z.dll, while artifact.jar wants to find it by its orginal, unversioned name.

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:

repositories {
  def cacheManager = new DefaultRepositoryCacheManager()
  cacheManager.name = 'dllArtifactCache'
  cacheManager.artifactPattern = "[organisation]/[module](/[branch])/[type]s/[revision]/[artifact](.[ext])"
  cacheManager.setLockStrategy(new NoLockStrategy())
  def resolver = new org.apache.ivy.plugins.resolver.URLResolver()
  addFirst(resolver) {
    name = 'dllrepo'
    m2compatible = true
    addArtifactPattern "[organisation]/[module]/[revision]/[artifact].[ext]"
    descriptor = 'optional'
    checkmodified = false
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:

  • 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 11:49:36 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.