JavaFX 11 snapshots in maven sonatype

Matthieu BROUILLARD matthieu at brouillard.fr
Sun Jul 8 19:30:42 UTC 2018


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/jgitver/jgitver
2: https://github.com/jgitver/jgitver-maven-plugin
3: https://github.com/jgitver/gradle-jgitver-plugin

On Sun, Jul 8, 2018 at 7:57 PM Sven Reimers <sven.reimers at gmail.com> wrote:

> 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 <swpalmer at gmail.com> schrieb am So., 8. Juli 2018, 19:04:
>
> > 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 <johan.vos at gluonhq.com> wrote:
> > >
> > > 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 anyhow,
> right?
> > >
> > > - Johan
> > >
> > >> On Sun, Jul 8, 2018 at 11:06 AM Kenzie Togami <ket1999 at gmail.com>
> > wrote:
> > >>
> > >> 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-jfx/pull/83/files#diff-c197962302397baf3a4cc36463dce5eaR1564
> > >> I haven't used the Gradle maven-publish plugin yet but I think it
> could
> > >> work if you instead iterate over each target where the artifacts are
> > >> generated, which is the only place it's used anyways:
> > >>
> > >> compileTargets { t ->
> > >>    artifact project.tasks."moduleEmptyPublicationJar$t.capital"
> > >>    artifact project.tasks."modularPublicationJar$t.capital" {
> > >>        classifier "$t.name"
> > >>    }
> > >> }
> >
>


More information about the openjfx-dev mailing list