Perhaps not adding any suffix to the version for the java8 version would be ok
and to add “java7” to the version for the legacy builds would be a good
compromise.
Chris
Am 08.06.17, 11:11 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
So, they are adding the java version as a suffix to the version of the
artifact … don’t quite know if I really like that solution. I think It would
break some version related automatisms, but it is definitely a safer solution
as the classifier solution. But how would such a build look like? Using version
properties everywhere except the pom type artifacts which are used as parents
by the leaf artifacts? That could work, but would it break anything with the
release-plugin?
Chris
Am 08.06.17, 11:04 schrieb "Maxim Solodovnik" <solomax...@gmail.com>:
Hello Chris,
Here is one example:
https://repo1.maven.org/maven2/org/postgresql/postgresql/
WBR, Maxim
(from mobile, sorry for the typos)
On Jun 8, 2017 10:44, "Christofer Dutz" <christofer.d...@c-ware.de>
wrote:
> Hi,
>
> Currently the Edgent project produces two tar.gz files … one for
java7 and
> one for java8. Now they would like to produce artifacts for
Maven-Central.
>
> I’m currently trying to help them with their build by migrating this
to
> maven. I think that there currently is no clean way to provide both
java7
> and java8 versions. We could add classifiers, but that would mess up
the
> dependency resolution mechanism.
>
> Do you guys know how other projects do this sort of thing?
>
> Chris
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
