Legal and practical constraints for using the openjfx-osgi p2 repository [message #1803488] |
Fri, 01 March 2019 14:30 |
Alexander Diewald Messages: 1 Registered: March 2019 |
Junior Member |
|
|
Good afternoon Tom,
First of all, thanks for your great work bringing JFX to the eclipse/EMF world.
I'm currently updating our e3-based RCP to the eclipse platform version 2018-12 and OpenJDK/OpenJFX 11. We are iteratively migrating to JavaFX to ease a later jump to a completely e4 & JavaFX-based RCP hosted at eclipse. (The RCP is a continuously developed "research prototype" of our group at our research institute)
For the migration updates, I've used your openjfx-osgi p2 repository at bestsolution.at to pull the required PDE and runtime artefacts. Up to now, this repository was just used internally to do the migration.
Before we publish / distribute anything using this repository, I would like to ask you if we are allowed to use the aforementioned repository since I did not find any terms for this p2 repository? (We don't have a support contract)
Second, is this repository about to stay, or is it just for testing?
If we are not allowed, we can also (and have to ;) ) switch to an alternate version we used for testing before. But less duplicates are always welcome :)
I'm posting this here, as this question might also be relevant for others.
Thanks in advance,
Alexander
P.S.: Since we also have a successor project hosted at eclipse: Is there already a statement from the Board of Directors regarding the dependency on OpenJFX (GPL+CE license)? OpenJDK is allowed AFAIK, but I did not find a statement for OpenJFX yet.
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03944 seconds