javafxpackager and launcher wrappers now in OpenJFX 8

Daniel Zwolenski zonski at
Sat Dec 22 12:04:05 PST 2012

I lodged a request for this yesterday:

I went with the GroupId of

Which seems to be the closest to the official domain for the project. I thought would have been nicer, but it doesn't appear to be registered?

If anyone has objections to this shout out quickly as I should be able to change it before first deploy. Once something is in the central repo though it's there for infinity and beyond - future versions can change/move but that old version will always be there confusing things. Best if it's right from the get-go. 

On 23/12/2012, at 4:19 AM, Richard Bair <richard.bair at> wrote:

>> The Sonatype guys (who we upload via) won't care if it is you or me (since
>> your licence gives me the right) but it will be deployed under the "javafx"
>> (or "javafx.deploy") groupId.
> I would suggest that you should use "openjfx.deploy" and not use "javafx.deploy". We should follow the pattern here of OpenJDK and Java. OpenJDK is the open source project, with its own distinct set of binaries from the commercial Java binaries. Likewise, JavaFX is the product that Oracle produces based on the OpenJFX bits. Even if/when we get to the point where the binaries are exactly the same, I'm sure the distinction will be something Oracle will want to preserve.
> But there's no problem producing OpenJFX builds and such.
> Thanks!
> Richard

More information about the openjfx-dev mailing list