[GRADLE-2553] Native Libraries are in the wrong directory Created: 14/Nov/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Stefan Wagner Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Dependencies defined like this:

  dependencies {
    compile 'org.jogamp.jogl:jogl-all:2.0-rc10'
    compile 'org.jogamp.jogl:jogl-all:2.0-rc10:natives-windows-i586'
    compile 'org.jogamp.jogl:jogl-all:2.0-rc10:natives-linux-amd64'

downloads the jars into separate folders (the folders have something like a hash as its name) but the jar with the class-files (first dependency) looks for the native library (depending on your system) in its own folder.

I can run the application if I move the native lib into the folder of the main jar.

This works under maven (tested with eclipse).

In an older gradle version (0.9) it just downloaded the last entry of the three dependencies above. It looks like at this time gradle couldn't handle dependencies with same groupId/artifact/version but different classifiers.

Comment by Stefan Wagner [ 21/Nov/12 ]

this is the URL for the maven repository: http://www.jogamp.org/deployment/maven/

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:25:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.