mvn deploy:deploy-file with same groupId & artifactId but different classifiers

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 deplo

Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

Hi, you can use the property -Dclassifier. For the Linux build I would use -Dclassifier=linux and for the Windows build -Dclassifier=win. Best regards, Sandra Am 29.06.2015 um 09:53 schrieb Francois MAROT: > Hello all, > > I'm in the process of converting an existing build to Maven. I have > 2

Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

Hi Francois, in my experience you will need to deploy from a single machine in a single call to deploy:deploy-file, attaching all the artifacts you need to deploy with qualifiers, e.g.: Use a single free form jenkins job to - synchronously trigger a multiconfiguration job in jenkins to build th

Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

Thanks Sandra, but I'm not sure I understand: I already use the -Dclassifier= parameter in the 2 command I copy/pasted above. Do you mean setting "linux"/"windows" instead of "natives-linux"/"natives-win" would change something ? I think classifiers are "form-free" and I kind of need the prefix "n

Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

I think you should have a look at the generatePom parameter ( https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#generatePom) which is true by default and should be false for the second call. Jeff On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot wrote: > Thanks Sandra, >

Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

@Jeff, thank you I think I'll try that. I thnink it will solve my "problem" @Wolf: you're totally right. That is the only solution I thought of before Jeff's. It's the cleaner solution, but as I'm in the middle of a migration, I will take some shortcuts to finish sooner. But at the same time I fear

RE: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers

Regardless of using Maven, I've always felt that for a multi-platform codebase, a build isn't successful/publishable/shippable if it hasn't succeeded on all required platforms (if the fix requires a change in the source code). So I've always favored the gather-and-deploy approach. > -Origin