I'm using artifactory-publish plugin for deploy the artifacts. Another Gradle build is using those artifacts by resolving latest version of it: compile (group: 'my.group', name: 'test1', version: '1.0.0+', ext: 'jar')
We're running some extensive testing and build very often. So sometimes we have situation, when the jar is beginning to be accessed while the publishing is not completely done. The Pom already exit, but jar is coming in 1 sec later. As result the build failed since it can download required jar. What is solution for that situation? How I can be sure that the jar is published before the jar? Can I configure the build to retry to resolve the jar, if it not exist/acceptable in the first place? Thanks, Samantha -- View this message in context: http://forums.jfrog.org/What-is-deployed-first-jar-or-Pom-tp7580429.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
