Daniel Zwolenski zonski at googlemail.com
Tue Dec 13 01:26:15 PST 2011

Seems the legal issue is solved! It would be great to get them in there!

Are you going to manage the deployments then (definitely fine by me) and do
you go via Sonatype or something else (actually I don't think you can use
Sonatype unless it is fully open source - what's your plan)?

How does it work with the fact that you don't own the domain/group (I've
only ever deployed stuff I've built) - will you need to get someone from
Oracle to ok it, or do the Maven guys just not care? There's that whole PGP
key generation stuff too, that has to be published. It would be good that
if you end up not able/willing to do the deploy in the future that
everything is setup for someone else (i.e. anyone on this list) to pick it
up and do it too. Maybe we need a small open source project somewhere that
is the pre-loader and PGP signatures (or whatever we need) , along with a
simple wiki on how to do it? Or could something like that be part of this
openjfx code base?

How do you add your pre-loader to it, do you rejar up jfxrt.jar with the
extra code and dll's into a new jar or do something else? It would be great
if there was a way to keep a 'pure' artifact that is the runtime jar
exactly as it comes from JFX, and then just have the preloader as a
separate artifact. Is this possible or does the preloader need to be in the
same jar/artifact to work?

I assume the group will just be 'javafx'. Will the artifact be 'javafx' or
'javafx-rt'? What's your thinking on per-platform native files: one
artifact for all platforms with a jar that contains all natives and just
extracts as appropriate, or a separate jar per platform?

Can I also put in a request that we get the 'ant-javafx.jar' (from the
'tools' directory of the install) added to maven as a separate artifact as
well. Maybe with artifact ID 'javafx-tools'. I use this for a very rough
skeleton of a JavaFX Maven plugin for assembly, that does all the packaging
stuff (i.e. put together a webstart app by calling the 'packager' classes).

I got this Plugin working (rough) but put it on hold because it needed this
tools jar and the licence stopped me from distributing it. Game on now! I'm
stretched for time until Jan at this stage (cursed day job, thinks it's so
important just cause it pays money, meh) so probably a Feb release at best
unless someone wants to collaborate on it (it's really not hard code to
write and I've got rough basics working)? Either way, I'd be looking for it
to go under the 'javafx' group when it is published so if you're the gate
keeper for this I'll need your help for the deployments at a minimum.

One other thought - can we also now be deploying these pre-alpha releases
of the 2.1 code, maybe just to the snapshot directory (i.e. use at own
risk)? If we can deploy regular (weekly?) snapshots of the openjfx 2.1
stuff it will make it real easy for developers to start testing it, and
people on this forum (who like maven) will be able to easily create test
apps and try out new features, ideas, etc.

Oh, and will the openjfx be under a different a group/artifact to the
Oracle one? I guess it would have to be.

Can you tell I'm a little bit excited about having a clean build again :)
It's like nerd christmas!

On Tue, Dec 13, 2011 at 6:21 PM, Tom Eugelink <tbee at tbee.org> wrote:

> So, now I can put the jars and DLL's in the Maven central repository???
> Say yes. Say yes.
> Tom

More information about the openjfx-dev mailing list