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.
> -----Original Message----- > From: Francois Marot [mailto:francois.ma...@gmail.com] > Sent: Monday, June 29, 2015 9:50 AM > To: Maven Users List > Subject: [EXTERNAL] 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 the "obscure > behaviour". Hope I won't face it soon ;) > @Sandra: no problem, at least thanks for helping ! > > On a more general discussion, what do you people think ? Is Wolf's solution > the closest to The Maven Way™ or is Jeff's solution totally acceptable (even > if > it's not, I'll take it for now !) ? > > > > - - - - - > > > *François Marot06-50-91-96-38* > > On 29 June 2015 at 11:18, Jeff MAURY <jeffma...@jeffmaury.com> wrote: > > > 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 > > <francois.ma...@gmail.com > > > > > wrote: > > > > > 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 "native-" in front of > > > it so that other parts of the build can handle those dependencies as > > > native > > ones > > > (for example this plugni: https://code.google.com/p/mavennatives/) > > > > > > > > > > > > - - - - - > > > > > > > > > *François Marot06-50-91-96-38* > > > > > > On 29 June 2015 at 09:57, Sandra Parsick <spars...@web.de> wrote: > > > > > > > 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 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- > grou > > pId-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 > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > --- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > > > > > > > -- > > Jeff MAURY > > > > > > "Legacy code" often differs from its suggested alternative by actually > > working and scaling. > > - Bjarne Stroustrup > > > > http://www.jeffmaury.com > > http://riadiscuss.jeffmaury.com > > http://www.twitter.com/jeffmaury > > ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
