JavaFX Maven Plugin
scott.kovatch at oracle.com
Sun Nov 25 11:25:32 PST 2012
On Nov 25, 2012, at 3:29 AM, Daniel Zwolenski <zonski at gmail.com> wrote:
> Hey guys,
> Is there any more news on the open sourcing of the packaging tools? It's
> been a "few days away" since October 27.
> What I'd really like to not have to rewrite are the native launcher
> executables that get bundled into the installers (i.e. the "exe" on
> windows). I can rip these out of the Java bundle for now to do my
> development but I won't be able to release my improved bundler until these
> bits are open sourced, giving me the legal all clear to include them in my
> Any chance I could get an actual timeframe on when the packaging tools are
> to be open sourced?
I'm chugging along with this, but I was off last week due to the US Thanksgiving holiday.
The code has been cleaned up (read: commented, TODO's removed/bugs created) and ready for review. There is some code we want to retire as part of this process, and that means modifying some makefiles and ensuring everything builds correctly in the closed repository, and then we can move it to the open rt project in OpenJFX and make sure it builds there.
So, it's happening, but there were some changes in assumptions I have to work around. Releasing something that won't build isn't helpful. I'll have a better timeframe early this week.
> I'm doing my best to contribute what I personally think is vitally
> important for JavaFX. In general I'm accepting of the fact that what I'm
> doing is not something Oracle sees as overly important and I'm on my own
> (it's been quite a liberating attitude to take to be honest). Open Sourcing
> the packaging tools however, was something you said you were going to do
> anyway and it would save me having to write a whole new native launcher for
> each platform.
I think it's great that you're interested in working on this. Deployment is not a glamorous job but it needs to be done. Without it, the rest of JavaFX isn't as useful, IMO.
What we want to do is have a core API that's as tool-ignorant as possible, and then let developers like you put the tool frameworks around it. Right now we're closely tied to ant, and I'd like to get away from that.
-- Scott K.
More information about the openjfx-dev