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
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
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
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
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,
>
@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
-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
>
> @Je
OK all, so I've taken the "not so clean but should solve my problem faster"
road... I publish the 2 zips separatly on Archiva.
But now, my main build that declare dependencies on them both (as 'runtime')
seems to randomly fail, looking for one or the other. If I publish one of
the 2, the main build
OK, so Maven only sees the most recent one uploaded because on Archiva, the
"maven-metadata.xml" file is updated each time with the timestamp of the
most recent one (either *-linux or *-win). But the 2 qualified artifacts do
not share the same timestamp so one of those is not found leading to build
