HEADS-UP: switching to gradle 1.8 for next week's build

Mario Torre neugens.limasoftware at gmail.com
Wed Nov 20 12:07:27 PST 2013

2013/11/20 Scott Palmer <swpalmer at gmail.com>

> I guess I don't quite understand the "packaging and distribution" process.
>  If the packaging and distribution runs gradlew instead of gradle, what
> does it matter if the project was changed to use a different version?
>  There will effectively be no dependencies that aren't resolved by the
> gradlew script (which is checked in with the source code) at build time -
> including the dependency on gradle itself.  Are the machines that this
> would run on not able to access the internet?

In short, you can't ship a package that start downloading stuff you don't
know about and don't control, all the dependencies need to be explicitly
packaged and shipped together. Also, anything that ships in binary form
needs to be buildable from sources.


pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

IcedRobot: www.icedrobot.org
Proud GNU Classpath developer: http://www.classpath.org/
Read About us at: http://planet.classpath.org
OpenJDK: http://openjdk.java.net/projects/caciocavallo/

Please, support open standards:

More information about the openjfx-dev mailing list