JFXtras also uses versioning based on the associated Java version, which works
quite well.
It can change based on what will be picked here. Or not. :-)
On 8-7-2018 21:28, Johan Vos wrote:
I agree.
It's not only the pragmatic approach (no need for a work-around for the
gradle snapshot/classifie
>I don't think that will help, as the artifacts for the different platforms
are not created inside the same gradle process. We don't do
cross-compiling, so for each compileTarget a different machine and a
different build process is used.
>Hence, I think we have to deal with separate publications an
Hi,
If you are really looking for some automated project versioning, you can
also look at jgitver (1) which can compute project versions based on git
commits, tags, branches, ...
There is a maven core extension (2) and a gradle plugin (3) for it.
-- Matthieu Brouillard
1: https://github.com/jgit
I agree.
It's not only the pragmatic approach (no need for a work-around for the
gradle snapshot/classifier combo issue), but it also makes it easier to
track issues (e.g. "this issue appears with 11.0.0-ea18 but is gone with
ea19) -> versioning in JBS/github.
- Johan
On Sun, Jul 8, 2018 at 7:37
Hi,
I think I like the idea of just having something similiar like OpenJDK e.g.
11.0.0-ea18.
Do we really need snapshots - i.e. continuous builds published to maven
central?
-Sven
Scott Palmer schrieb am So., 8. Juli 2018, 19:04:
> If separate Gradle processes produce the artifacts, there is p
If separate Gradle processes produce the artifacts, there is probably a way to
bring them together and (re-)publish them together in yet another project.
Scott
> On Jul 8, 2018, at 8:38 AM, Johan Vos wrote:
>
> I don't think that will help, as the artifacts for the different platforms
> are n
I don't think that will help, as the artifacts for the different platforms
are not created inside the same gradle process. We don't do
cross-compiling, so for each compileTarget a different machine and a
different build process is used.
Hence, I think we have to deal with separate publications anyh
Hi Johan,
> It is very inconvenient, so if you know an easy way to get all snapshot
version to be equal, I would love to hear that.
I think that the varying snapshots versions probably occur because a
separate publication is set up for each `compileTarget`:
https://github.com/javafxports/openjdk-
If you deploy it as a release, Sonatype won't allow overwriting, right? So its
behavior is different from a snapshot and you can't overwrite it each night.
Maybe frequently releasing EA builds is acceptable for Gradle, and Maven can
still use snapshots?
Or can Gradle be told to use a specific sn
