If the actual name of your module is ProjectA, you might be better off
defining "abc" as a classifier.
See here<http://gradle.org/docs/current/userguide/dependency_management.html>and
here <http://gradle.org/docs/current/userguide/working_with_files.html> for
more info.
On Wed, Jul 11, 2012 at 12:25 AM, Tinkerer <[email protected]> wrote:
> A snippet of my original build.gradle file for 'ProjectA' (foldername:
> ProjectA) has -
> apply plugin: 'java'
> group = 'myGroup'
> archivesBaseName = 'ProjectA-abc'
> version = 'SNAPSHOT'
> ...
> This results in a jar artifact named ProjectA-abc-SNAPSHOT.jar
>
> I am using the gradle-artifactory plugin to publish to the Artifactory
> repo.
> The upload url looks like this -
>
> http://artifactory.xyzcorp.com:8080/artifactory/xyz/myGroup/ProjectA/SNAPSHOT/ProjectA-abc-SNAPSHOT.jar
>
>
> In a separate project, that consumes ProjectA's jar, my build.gradle has -
> ..
> dependencies {
> compile(group: 'myGroup', name: 'ProjectA', version: 'SNAPSHOT',
> ext:
> 'jar')
> }
>
> When I type gradle build, the build fails to resolve the dependency.
> Analyzing the Gradle log shows that it's trying to do a GET request to the
> resource at
>
> http://artifactory.xyzcorp.com:8080/artifactory/xyz/myGroup/ProjectA/SNAPSHOT/ProjectA-SNAPSHOT.jar
> , which does not exist and fails!
>
>
> Changing the above dependency to use name: 'ProjectA-abc' , instead, leads
> to another similar failure -
> ..
> dependencies {
> compile(group: 'myGroup', name: 'ProjectA-abc', version:
> 'SNAPSHOT', ext:
> 'jar')
> }
>
> The GET request in this case is to the resource at
>
> http://artifactory.xyzcorp.com:8080/artifactory/xyz/myGroup/ProjectA-abc/SNAPSHOT/ProjectA-abc-SNAPSHOT.jar
> , which does not exist and fails too!
>
> Is there a way I could influence the url that is being constructed so that
> the consumers of my artifacts can get to my Project-abc-SNAPSHOT.jar
> without
> failing? Something like Project.name = 'Project-abc' instead of using
> archivesBaseName property from the java plugin.. Pls advise.
>
> --
> View this message in context:
> http://forums.jfrog.org/Gradle-fails-to-resolve-dependencies-when-using-archivesBaseName-tp7578086.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users