Producer project (producer) publishes 3 different artifacts (A.exe, B.zip,
C.zip) using a single confuration into Artifactory repo- 
...
artifacts { 
      producerArchives file: file("${buildDir}/A.exe"), name: "A", type:
'exe', builtBy: execTaskA
      producerArchives file: file("${buildDir}/B.zip"), name: "B", type:
'zip', builtBy: zipTaskB
      producerArchives file: file("${buildDir}/C.zip"), name: "C", type:
'zip', builtBy: zipTaskC    
}
artifactoryPublish { .. }

When I look inside Artifactory I see all 3 of my artifacts - 
myGroup/producer/SNAPSHOT- 
--- A.exe 
--- B.zip 
--- C.zip

In my Consumer project (consumer) my dependency block looks like this - 
...
dependencies {
        getIt(group: 'myGroup', name: 'producer', version: 'SNAPSHOT', ext:
'exe') 
        getIt(group: 'myGroup', name: 'producer', version: 'SNAPSHOT', ext:
'zip')    
        /* getIt(group: 'myGroup', name: 'producer', version: 'SNAPSHOT',
ext: 'zip')  */
}

which leads to "Could not resolve all dependencies for configuration
':getIt'.. " error.

Running with -d (debug log) shows a GET request for resource - 
GET /artifactory/repo/myGroup/producer/SNAPSHOT/producer-SNAPSHOT.zip 
which does not exist, hence the error. How might I approach this
differently?



--
View this message in context: 
http://forums.jfrog.org/Could-not-resolve-all-dependencies-when-publishing-multiple-artifacts-from-a-single-project-tp7578143.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

Reply via email to