hg: openjfx/2.1/master: Added build scripts that are needed for building UI controls.
richard.bair at oracle.com
Tue Dec 6 11:39:58 PST 2011
> On 2011-12-06 19:28, richard.bair at oracle.com wrote:
>> Added build scripts that are needed for building UI controls. Actually they are probably not ALL needed, but they don't hurt. We need to clean these things all up as part of the open sourcing process, since the mechanism by which we download and install the necessary libs are probably going to be different than what we have been doing up to this point.
> May I suggest that if the build process is refactored, it is smart to be focussing on generating artifacts. I do not really care if that is done using ANT & Ivy, Gradle or Maven, but I think generating Maven compatible artifacts with dependency information is very wise.
The way this works in our internal builds is that:
- We have some 200+ individual NB projects which span everything from samples, demos, performance tests, and actual production code.
- Each NB project produces both myproject/build/... class files as well as myproject/dist/myproject.jar file
- The larger system them builds these into artifacts/, such that there is a full & complete SDK (minus the installer)
We use Ant for all the builds, although there is some concern about how we'll go about doing things when we get integrated into the JDK (where they use make... yikes!). We use a little make as well for building the native parts (media, webkit, glass).
I think modifying the build scripts so that they also produce maven-compatible artifacts is fine, I know this has been asked for frequently. We don't know how to do it though (I don't know any of our team that has any significant time in Maven).
Any large changes to the build system though will need to be done very deliberately so as not to disrupt the engineering team or deliverables for 2.1 or 2.2. But it would probably be a worthwhile exercise to collect the requirements for the system.
More information about the openjfx-dev