Eclipse adalah software open source yang digunakan untuk mengembangkan IDE (Integrated Development Environment), software Java IDE disebut Java Development Toolkit (JDT) software yang digunakan untuk membuat program java selain java software ini juga dapat digunkan untuk membuat program aplikasi android dengan tambahan beberapa plungins. Eclipse awalnya dikembangkan oleh IBM, tetapi sekarang dikembangkan oleh Eclipse Foundation. Banyak vendor software yang menggunkan Eclipse sebagai kerangka masa depan IDE, di antaranya Borland dan IBM Rational.
Persyaratan :
· Setiap hal berikut:
· Sun Java 2 Standard Edition 5.0 Update 11
· IBM SDK 32-bit untuk Windows, Java 2 Teknologi Edition 5.0, SR4
· BEA JRockit 5.0,
· Sun Java 2 Standard Edition 1.4.2_14
· IBM SDK 32-bit untuk Windows, Java 2 Teknologi Edition 1.4.2 SR7
· BEA JRockit 1.4.2
Yang Baru dari Eclipse :
Platform:· Migration Wizard: Building on the changes introduced in M5 to detect changes in shared installs, Eclipse now includes a migration wizard to help users through the re-ininstallation of their plug-ins.
· This wizard is presented in two situations. First, when a read-only installation of Eclipse is being changed (i.e. Eclipse is being updated or plugins are added / remove), second when a new read-only installation of Eclipse is run for the first time.
· BIDI Text Direction: New API has been added to allow text direction to be set independent of the widget orientation. For more info see Snippet 364.
· New SWT color constant for hyperlinks: A new constant (SWT_COLOR_LINK_FOREGROUND) has been added that will return the native color of hyperlinks on all platforms.
· Whole word option on File Search page: The File Search page now allows to search for words via a new option.
Open Search dialog on last used page: The Search dialog can now be configured to open on the last used page, instead of computing the best matching page based on the current selection:JDT:· 'Convert to if-!-return' Quick Assist: Ever encountered a long if statement that can be safely inverted to an early return, so that you can ignore the code that follows, and make it easier to understand? Now, you can just use a Quick Assist (Ctrl+1) on the if statement to do this refactoring.
· Package names are linked in Javadoc hover and view: You can now click individual package names displayed in the header of the Javadoc hover or the Javadoc view to see the package Javadoc.
· Javadoc and Declaration view indicate when out of sync: The Javadoc and Declaration view now indicate when their content is no longer in sync with the current selection.
· Only one JUnit (4.11): The org.junit bundle has been updated to JUnit 4.11. At the same time, our good old friend org.junit_3.8.2 has been retired, and the org.junit4 compatibility bundle has also been removed. Your Require-Bundle: entries should just point to org.junit;bundle-version="4.11.0" (or an earlier version, if you like). Note that JUnit 4 still contains the JUnit 3 APIs. If you need org.junit_3.8.2 back for whatever reason, you can still get it from Orbit.
· Improved evaluation of generics while debugging: Significant improvements have been made in the debug evaluation engine to support the use of generics. This impacts the use of conditional breakpoints, the display view, the expressions view, and the inspect/display/execute actions. Previously, evaluations acting on classes with generics would sometimes encounter compilation errors.
· API to contribute location information for non-standard JRE / JDK libraries: JDT Debug now provides an extension point org.eclipse.jdt.launching.libraryLocationResolvers that you can use to contribute location information for non-standard JRE / JDK libraries. For example, this extension point can be used to provide Javadoc and source locations for JARs in the ext location of a JRE. Extenders must provide an implementation of org.eclipse.jdt.launching.ILibraryLocationResolver which can provide package roots, source paths, Javadoc locations and index locations for a library.
PDE:· API Tools Analysis and Freeze tasks can run with unresolved bundles: The API Tools Analysis and API Freeze Ant tasks will now process bundles with resolver errors such as missing dependencies. This means you can now get analysis results for an incomplete product. The Ant tasks produce reports based on a reference baseline and a profile. Previously both the baseline and the profile had to describe complete products. Any bundle that had resolver errors due to missing dependencies would be skipped. Now these bundles will be processed. Resolver errors can affect the results, therefore a list of resolver errors is included in the XML output and warnings are added to the HTML report. To return to the old behavior of skipping unresolved bundles, you can set processunresolvedbundles="false" on your Ant task.
