Migrate to Gradle wrapper build

[pdavidc]

Migrate World Wind Java to a Gradle wrapper based build system. Gradle builds integrate fully with the IntelliJ IDE internal build system, eliminating the duplicity of separate IDE build and ANT build process.

[AndrewTasso]

This would be awesome!

Unfortunately, there's a bit of a chicken and the egg situation here. Gradle relies heavily upon convention to operate easily. The WorldWind project doesn't adhere to the conventions that Gradle expects too well. Fortunately, Gradle can be bent to your will, but it might be a bumpy road in doing so.

Some things to watch out for when migrating to gradle:

• Utilization of local jar dependencies instead of maven based dependencies
• Source (main and test) not in expected maven location
• Resources (images, config, etc) not in expected maven location
• WebStart doesn't have first class support, and will require a plugin
• Distributable being bundled into a fat jar instead of using transitive dependencies

I've been using Gradle for a few years now, so I'd be glad to provide any input/support if you'd like.

[pdavidc]

Andrew, Thanks for your feedback, and this input on switching to Gradle.

Our plan is indeed to adopt the Gradle conventions where it's either necessary or in our best interest. I appreciate the offer of input/support, and may reach out when the NASA team has time to make the transition.

[wcmatthysen]

Hi @AndrewTasso. Would appreciate it if you could help us with this. We have a community-edition of WorldWind up and running at: https://github.com/WorldWindEarth/WorldWindJava. We plan on using Gradle to build and manage dependencies. The issue is logged at: https://github.com/WorldWindEarth/WorldWindJava/issues/11