RSS
 

Posts Tagged ‘java’

Google Gives $5M Worth of Java GUI Tools to Eclipse

19 Dec


Google has donated two open-source Java tools to the Eclipse Foundation to join the popular IDE suite in 2011.

The tech giant’s WindowBuilder and CodePro AnalytiX were part of Google’s acquisition of Instantiations in August this year. By September, Google had relaunched some of Instantiations’ tools as open-source software.

One of those tools was WindowBuilder, a WYSIWYG code generator. This drag-and-drop, bidirectional GUI designer for Java played nicely with a variety of frameworks, including Swing, XML Windowing Toolkit (XWT), the Standard Widget Toolkit (SWT) and more. With support for Windows, Linux and Mac, the Eclipse extension was intended to make Java app creation a lot simpler and faster.

And CodePro is another interesting Eclipse plugin for “comprehensive automated software code quality and security analysis.” The toolkit included features from EclipsePro Audit and EclipsePro Test and generally attempted to improve code quality, maintenance and readability.

Instatiations’ execs estimate the software, which is slated to roll out with the rest of the Eclipse June 2011 release train, is worth around $5 million.

Google’s emphasis on Java tools is hardly surprising; the blockbuster success of the Android platform (and sometimes harsh criticism of the Android Market of apps) has practically mandated a focus on Java, which is a big part of the Android stack. Giving devs better Java tools free of charge is an investment in the future of Google’s own platforms.

That’s not to say either of these Eclipse extensions is, in itself, going to be directly used for Android applications; we’re not sure either tool is intended for mobile development. But better tools make better Java devs, who in turn are better equipped to make more and better Android apps.

We would, however, love to see more drag-and-drop, WYSIWYG-plus-code Android app tools — something along the lines of a less-dumbed-down App Inventor. If you know of any such tools, definitely let us know about them in the comments.

Reviews: Android, Android Market, Eclipse, Google, Linux, Windows

More About: codepro, developers, eclipse, foss, Google, java, open source, windowbuilder

For more Dev & Design coverage:

 
No Comments

Posted in Google Reader

 

Apache quits Java governance group in protest of Oracle abuses

09 Dec

The Apache Software Foundation (ASF) announced today that it is resigning from the executive committee of the Java Community Process (JCP), the governance body responsible for managing standards related to the Java programming language. The move is a response to Oracle's ongoing failure to comply with the intellectual property policies established by the JCP.

The heart of the issue is that Apache can't certify that its open source Java implementation—called Harmony—conforms with the Java language standards because Oracle refuses to supply the necessary test suites under a suitably open license. Oracle's position on the issue falls afoul of JCP policies, which stipulate that standards and other relevant materials must be freely redistributable and made available under terms that are conducive to enabling third-party open source implementations.

Read the rest of this article...

Read the comments on this post

 
No Comments

Posted in Google Reader

 

Google Just Lost a Potential Ally in its Legal Tussle with Oracle

12 Oct


The battle between Oracle and Google over Android’s use of Java just got a lot more interesting. That’s because IBM has announced that it will be collaborating with Oracle to work on the OpenJDK project.

This means that IBM will no longer be part of the Apache Software Foundation’s Project Harmony, the project that provides Android with the components it needs to run Java code. With IBM leaving the project, Harmony is basically dead in the water.

Although Android wasn’t mentioned in the announcement, this is all interrelated to the Oracle lawsuit. Google responded to the lawsuit last week, claiming that Oracle, which got Java out of its purchase of Sun Microsystems, was acting in bad faith.

For the non-Java savvy out there, here’s an abbreviated rundown of how and why all of this stuff matters:

Apache Harmony is an open source implementation of Java. The goal in creating the project was to unite all of the various free software Java implementations together under one banner.

The project had a lot of early support, the only problem was that Sun (and then Oracle) never offered the project with a Technology Compatibility Kit (TCK). The TCK is needed to prove that Harmony is compatible with the Java specification and can be seen as a certified Java independent version of Java. When Sun first open sourced aspects of Java in 2007, it said it would provide the Apache Foundation with the necessary TCK for certification.

Sun never made good on those assurances and when Oracle took over Sun, the new company wasn’t interested in sharing the TCKs, instead wanting to focus all of its efforts on the officially sanctioned open source Java implementation, OpenJDK.

IBM’s Bob Sutor discussed the decision on his blog, writing:

“We think this is the pragmatic choice. It became clear to us that first Sun and then Oracle were never planning to make the important test and certification tests for Java, the Java SE TCK, available to Apache. We disagreed with this choice, but it was not ours to make. So rather than continue to drive Harmony as an unofficial and uncertified Java effort, we decided to shift direction and put our efforts into OpenJDK. Our involvement will not be casual as we plan to hold leadership positions and, with the other members of the community, fully expect to have a strong say in how the project is managed and in which technical direction it goes.”

This is a big blow to the Harmony project and by extension, to the libraries and classes that Android implements from Harmony in Android. Without big backing like IBM behind the project, it’s not likely to survive.

For now, the Harmony implementation of Java is fine. The problem will be when future versions of Java are released and Harmony can’t keep up in terms of features.

In Java, staying compatible is key. Interestingly, InfoWorld notes that Google has more developers working on OpenJDK than Oracle. So why choose Harmony for Android?

We think it’s because Google wanted to do an end-run around Sun’s licensing requirements. In essence, getting to take advantage of Java SE on mobile devices (something that Sun explicitly forbade without a license), but not having to pay for it.

Long before Sun’s sale to Oracle, others pointed out the potential licensing and IP quagmire that Google was entering with Android. The reality was, Sun didn’t have the power, the funds or the industry clout to really do anything about it.

Oracle does. In fact, Oracle’s clout and power is underscored by IBM’s decision to join up. IBM may be making its decisions for pragmatic reasons, but in the decision shows that IBM is not willing to side with Google in this elongated fight.

At this point, Google’s only real recourse is to sensibly settle and pay Oracle, or countersue and drag the fight out even longer. By fighting back, Google risks alienating its Java-base of developers.

While we question how important having a strong base of Java developers really is to Android’s success in the long term, it doesn’t mean it’s worth risking the future developments of the platform on a legal gamble.

Oracle is out for blood and IBM just provided the syringe.

Reviews: Android, Google

More About: android, apache foundation, Google, harmony, IBM, java, lawsuits, legal, oracle

For more Tech coverage:

 
No Comments

Posted in Google Reader