Hello all, I'm in the process of converting an existing build to Maven. I have 2 Jenkins jobs building the same native library on 2 different systems (win / lin). At the end of each one, I want to deploy them on my Archiva repo. So I execute the following commands :
On a Linux computer: mvn deploy:deploy-file -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 -DrepositoryId=archiva.internal -Durl=http://centos-dev:8090/repository/internal/ On a Windows computer: mvn deploy:deploy-file -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 -DrepositoryId=archiva.internal -Durl=http://centos-dev:8090/repository/internal/ Problem is the second command leads to a "build failed" because the pom of the project in version 1.0.0 is already deployed... BUT, I am lucky because the artifact with classifier "natives-win" has already been uploaded so both artifact end up on the server correctly. So builds depending on them can retreive them correctly and everything is fine... ... except that I don't want to base my build on luck and would like to know what is the correct way to deploy 2 artifacts with everything being the same except the qualifier. How do you pepole deploy a same artifact but built by different computers, architectures ? I'm using Maven 3.3.1 & Apache Archiva 2.1.1 -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
