I thought I replied to the list, and not just you.
Probably easier to use the module name as artifactId, but it seems odd
though and stands out against all the rest of dependencies naming using a
dash delimiter.
Den tor. 5. jul. 2018, 19:02 skrev Johan Vos :
> The name is the same name as the
Gerd
>>> >
>>> > Gerd Müller-Schramm
>>> > Software Developer, GeoMedia Smart Client Kommunal
>>>
>> > T: +49 341 92 60 30 47 <+49%20341%2092603047> <+49%20341%2092603047>
>>
>>
>>> > E: gerd.mueller-schr...@hexagon.com
&
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:
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
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
>> >
>> > Hexagon Geospatial
>> > Wittenberger Straße 15B
>> <https://maps.google.com/?q=Wittenberger+Stra%C3%9Fe+15B+%0D%0A+04129+Leipzig,+Germany=gmail=g>
>>
>> <https://maps.google.com/?q=Wittenberger+Stra%C3%9Fe+15B+%0D%0A+04129+Leipzig,+Germany=g
Germany
> > hexagongeospatial.com
> >
> > -Original Message-
> > From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On
> Behalf
> > Of Johan Vos
> > Sent: Donnerstag, 5. Juli 2018 11:03
> > To: openjfx-dev@openjdk.java.net List
&g
jfx-dev-boun...@openjdk.java.net] On
Behalf Of Johan Vos
Sent: Donnerstag, 5. Juli 2018 11:03
To: openjfx-dev@openjdk.java.net List
Subject: JavaFX 11 snapshots in maven sonatype
A first batch of snapshots for the JavaFX 11 modules is now in the maven
sonatype snapshot repository (see
https://oss.son
;
>> Hexagon Geospatial
>> Wittenberger Straße 15B
>> 04129 Leipzig, Germany
>> hexagongeospatial.com
>>
>> -Original Message-
>> From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On
>> Behalf Of Johan Vos
>> Sent: Donner
Hi Johan,
many thanks for the clarifications.
Please find some more comments inline:
Am 06.07.18 um 14:54 schrieb Johan Vos:
Hi Michael,
Thanks for testing this.
You can avoid downloading all platform jars by specifying the
javafx.platform with maven:
mvn -Djavafx.platform=mac clean
Hi Michael,
Thanks for testing this.
You can avoid downloading all platform jars by specifying the
javafx.platform with maven:
mvn -Djavafx.platform=mac clean package exec:java
There is a rationale behind this:
maven would be able to detect the OS and make sure only the platform jars
related
va.net] On Behalf
> Of Johan Vos
> Sent: Donnerstag, 5. Juli 2018 11:03
> To: openjfx-dev@openjdk.java.net List
> Subject: JavaFX 11 snapshots in maven sonatype
>
> A first batch of snapshots for the JavaFX 11 modules is now in the maven
> sonatype snapshot repository (see
&g
Hi,
I tried the examples on my Mac with Maven and with a simple
mvn clean package exec:java
on the command line they all compiled and worked out of the box.
Great work! I used OpenJDK 11ea20 for this.
I have a few questions though:
1. I observed that maven downloaded all dependencies for
--Original Message-
From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of
Johan Vos
Sent: Donnerstag, 5. Juli 2018 11:03
To: openjfx-dev@openjdk.java.net List
Subject: JavaFX 11 snapshots in maven sonatype
A first batch of snapshots for the JavaFX 11 modules is now in
A first batch of snapshots for the JavaFX 11 modules is now in the maven
sonatype snapshot repository (see
https://oss.sonatype.org/content/repositories/snapshots/org/openjfx/ although
you probably don't want to work with these artifacts directly but use build
tools like maven or gradle to do
16 matches
Mail list logo
