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
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
