Agreed.
On Mar 27, 2018, at 8:16 PM, Pedro Duque Vieira
wrote:
Like Kevin says I don't think this is a one or the other choice.
I think we need to think about people who are just evaluating the platform
or learning, and whether making them also have to learn about build tools
is good.
I'd sa
Like Kevin says I don't think this is a one or the other choice.
I think we need to think about people who are just evaluating the platform
or learning, and whether making them also have to learn about build tools
is good.
I'd say part of the web's success is it shallow learning curve, and why
la
Ultimately, I think you are right that a standalone JavaFX needs to be
discoverable and usable via a dependency manager like gradle or maven.
From the discussion, it seems most others agree.
I note that this doesn't preclude also making a zip bundle available for
developers who want to downloa
>
> > (including property files and native code), he uses his build tools (e.g.
> > maven/gradle) to manage the download/install//update of those
> > libaries/frameworks.
> > If you rely on Spring, Apache Commons, slf4j,... you don't download those
> > SDK's but you point to the group-name-version
On 2018-03-26T11:28:44 +
Mario Ivankovits wrote:
> +1 on providing JavaFX as „simple“ dependency.
>
> Question is how to deal with the native libraries. Provide an artifact per
> platform?
Take a look at how LWJGL handles it:
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.lwjgl%2
+1 on providing JavaFX as „simple“ dependency.
Question is how to deal with the native libraries. Provide an artifact per
platform?
compile: 'javafx:javax.graphics-osx:11.0.0'
compile: 'javafx:javax.graphics-win:11.0.0'
compile: 'javafx:javax.graphics-pi:11.0.0‘
These bundles might just contain
Hi Johan, hi all,
in my opinion SDKs are tolerable for providing the fundamental layers of
infrastructure. But other dependencies should be lightweight and use the
default channels for providing dependencies. There should be no difference
between consuming JavaFX and let's say CommonsIO as depende
+1 for getting it the "normal" way..
Sven
Tom Eugelink schrieb am Mo., 26. März 2018, 10:59:
> I totally assumed that, when JavaFX is separated out, it will distributed
> as an artifact on Maven central (or similar) so it can be included like a
> dependency. Feels like a no brainer?
>
>
> On 26
I totally assumed that, when JavaFX is separated out, it will distributed as an
artifact on Maven central (or similar) so it can be included like a dependency.
Feels like a no brainer?
On 26-3-2018 10:50, Johan Vos wrote:
Hi,
I want to start a discussion on distributing JavaFX as an SDK vers
Hi,
I want to start a discussion on distributing JavaFX as an SDK versus
distributing its modules via the traditional build and distribution
mechanisms.
Personally, I think relying on an SDK is too much a barrier. It requires
users to manually download software from the exact right place, and
"in
10 matches
Mail list logo
