Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Migrating from Java to Groovy with NetBeans IDE 6.7

DZone's Guide to

Migrating from Java to Groovy with NetBeans IDE 6.7

· Java Zone
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!

One small enhancement in the upcoming NetBeans IDE 6.7 release is brand new built-in support for changing file extensions of existing files. That was never possible before.

Being able to change the extension of a file is pretty useful when you're converting a Java source file to a Groovy source file. The editability of the file extension that you see below is only available from 6.7 onwards (click to enlarge):

After changing the file extension, you simply need to specify in the Java application's Project Properties dialog that you're working with Groovy. By selecting the checkbox shown below, the Groovy JAR is added to the application classpath and the build.xml is changed so that the Groovy code and the Java code compile correctly (click to enlarge):

And then... you can begin weeding out all the superfluous Java code from your Groovy source file, paring it down to Groovy minimalism and then beefing it up to benefit from Groovy's syntactic sugar and its many other innovations!

 

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}