Milestone Summary of eclipse and myeclipse

Eclipse 3.4m7, the last milestone with complete features, was released in May 9. This version has made multiple improvements to the previous version of eclipse 3.3. By the end date of eclipse3.4 (Ganymede), we will have many candidates for release.

SWT-supports the eclipse UI Layer. Now you can create a full-screen window for the kiosk-mode application, or create a pop-up window that can be transparent or other HUD types (HUD-type) window. This allows the window to be displayed as a non-rectangle by creating a path in the opaque area. This technology is also applied to controls (such as buttons), although there is actually a three-state selection box that looks more useful. SWT can now run in a 64-bit Windows system + 64-bit JVM environment, although it can still run 32-bit SWT in a 64-bit Windows system + 32-bit JVM environment.

The Java tool has also been improved. The most important thing is the multi-threaded compiler that can improve performance when building a multi-core system. Unfortunately, this project is not built in parallel-as before, each part is built independently-but the actual compilation of each project can use multithreading. There are other advantages, such as restructuring expressions like A + B + C into equivalent stringbuilder/stringbuffer or messageformat statements, which are useful in many occasions. In addition, some other refactoring features have been added, such as restructuring a set of variables into a accessining class with accessors. You can drag and drop elements in the Outline View to re-sort the elements. The JUnit timing result reports how long each test case has been running, which gives us a rough judgment on the location of any performance issue. Finally, the automatic prompt function of the method is now added with a valid parameter value annotation, so when you use SWT to write code, A large number of new SWT templates (with common values in the "Flags" Domain) will be helpful.

For RCP development, the good news is that the log view is eventually moved to its own bundle, which means you can deploy it with the RCP application, instead of introducing the entire workbench. The Help System (infocenter) has been re-designed so that it can be inserted into any existing application server (such as jetty, tomcat, or SSAP ). In addition, the enhanced PDE can help to build documents for articles on the help center or eclipse.org. Finally, secureplatform can now be integrated with JAAS.

PDDE provides many enhancement features to format and refactor plugin. XML and osgi manifests, including other refactoring features that can help keep manifest up-to-date (for example, executing an import or adding appropriate entries during Code Completion), facilitate development. Plug-in spy, which has been in the incubator for a period of time, is now released together with 3.4 by default. With it, it is easier to use existing plug-in. Finally, for those who want to cut eclipse, the source bundle is now released as multiple separate units, rather than publishing in a huge bundle as before, this makes it easier for you to get the code you are interested in and ignore the code you are not interested in. The enhanced plug-in registration view allows you to stop or start bundles (and its osgi services), although they are not dynamically installed or removed.

There are still some changes to this platform. The most noteworthy is P2, a new eclipse supply platform (provisioning platform ). This is a substitute for the old update manager. Bundle and non-bundle components (such as configuration files, installation files, and drawing resources) are allowed to be installed or updated. It has many new features, such as viewing and verifying product digital signatures, downloading from images (or supply sites), or from multiple available products (such as pack200 and GZ) select the best-performing product. P2 also allows the dropins Directory, which is easier to install Bundle: just copy the bundle to this directory, eclipse will automatically install and activate it (of course, it depends on the license ). Eclipse may also be configured to share bundle mode, which makes a bundle library available and the bundle library will serve different applications. For those who use eclipse in general usage, this does not show any benefit, but if you are developing (or supporting) RCP applications ), there are many RCP-based applications installed on the same machine (for example, an internal suite of RCP applications [in-house suite]), you can share these bundle among multiple applications, which saves much space.

You can read various news and follow pages (M1, M2, M3, M4, M5, M6, and M7), which describe these features in more detail. From now till the end of June, many candidate versions with incorrect fixes will be released one after another. The end of June is the expected release date of Ganymede.

Eclipse prepares for 3.4 with feature complete milestone release

 

Important features of myeclipse 6.5m1

Myeclipse 6.5 M1 has many enhancements in functionality and usability, including portal support, enhanced JSF/facelets visual editor, spring tools (Spring 2.5 Library) and JAX-WS 2.0 WebServices. The official version of myeclipse6.5 is expected to be released in June, including support for Maven (planned ).

JSF/facelets

• • Enhanced Preview
  • Custom facelet Library
  • Enhanced JSF config Editor
  • Web. XML editor
• Portlets
  • Portal Project Wizard
  • Portlet wizard
• JAX-WS 2.0 web services framework support
  • Web Services Project Wizard
  • Top down/bottom up services generation
  • Clinet generation
• Spring tools
• Spring 2.5
• Explorer
• AOP support
• Refactoring
• Validation Control
• Mylyn Integration
• Web flow

JSF designer: enhances the myeclipse page designer to provide a preview so that you can see the effects of the facelets page, including the location and composition.

Preview the extended JSF tags that can also be rendered, including the MyFaces Tomahawk Library

Custom facelet Library: The page editor can also use the code prompt (context assitant) and verification when editing TLD.

Enhanced JSF configuration file editor: added editing and navigation functions in the JSF configuration file editor.

Web. XML editor: The new web. XML editor makes editing and navigation easy.

Portal Project Wizard: The portal wizard allows your existing web applications to be deployed as portals compatible with jsr168.

Portlet Wizard: the Portlet wizard can create a predefined Portlet project.

JAX-WS 2.0 support: myeclipse6.5 introduced support for the JAX-WS framework, which is based on Metro 1.1. Metro is the reference implementation of javaee 5 for JAX-WS. It supports Web Services and Web Services client programs that include top down and bottom up.

New Web Service Project Wizard: You can create a web services project or add web services support in an existing myeclipse web project.

Generate top down and bottom up services: Web services can be generated through WSDL or existing JavaBeans

Top down generation: Specifies a WSDL file to generate a web service.

Web. xml and sun-jaxws.xml are updated in Web Service generation

Note: If the service you deploy does not contain the JAX-WS stack, you must add the jar package of the JAX-WS and the runtime class library to your project; otherwise the operation will fail.

Bottom up generation: the Web service client can be directly generated using the WSDL file.

JAX-WS 2.1 APIs and runtime containers need to be added to client projects

Spring: myeclipse 6.5 spring tool is based on Spring ide 2.0.4 and is enhanced and optimized to seamlessly integrate with myeclipse application development.

Spring 2.5: added spring 6.5 support for myeclipse. Version 6.5m1 uses spring 2.5.4.

The spring 2 library is also updated to version 2.0.8.

Spring Explorer: the spring beans view is replaced by the spring explorer view. Spring Explorer is a filtering tree that displays all spring projects in your workspace, including any beans, config sets, and spring web flow elements. This view is namespace aware that can be customized and filtered.

The spring explorer view can comment out any bean configured through spring or Java.

Project Explorer: In the project explorer view, all spring projects contain a "spring element ". This extension is used to display the definitions of beans, config sets, and Web flow, as described in spring explorer. This capability helps all bean lists reference specific Java classes and is also a key feature.

Like spring explorer, spring elements can also be customized and filtered. You can also use a special spring working set to remove clutter in project explorer.

AOP support: the cross-reference view of beans shows how all beans are used by advise (according to the AOP term, no proper Chinese characters can be found. All AOP terms are in English .)

The spring configuration editor and Java editor can also display special marks, indicating that the methods and classes are affected by your AOP configuration.

The Spring AOP event tracking view will give you a deep truth through the built-in spring ide internal AOP model.

AOP support requires the AOP reference model builder, which can be enabled or disabled at the project layer or global layer. If you do not use AOP in the project, you can disable it during global settings.

Pointcut matches: added the pointcut matches function in bean search, which can be found in the search menu.

Namespace support: the new spring bean definition wizard allows you to easily use namespaces when creating configuration files.

The spring configuration editor is also namespace self-sensing and provides code prompts and verification functions.

Refactoring: Renaming the Java file will automatically change in the bean definition. Changing the name in bean configuration also affects the name of the Java file.

The bean ID is also renamed.

Renaming the bean property will change the corresponding Java file.

Verification control: You can set (Project Properties> myeclipse> spring) in the project layer or on the global layer (WINDOW> preferences> myeclipse> spring)

Mylyn integration: If you inherit from mylyn, the spring explorer, beans cross references, and project explorer views will let you filter the display content.

Spring web flow: myeclipse 6.5 also supports spring web flow. The M1 version currently uses the spring web flow 1.0.5 library.

Web flow Editor: Use a Graphical Editor to create States, actions, and transitions.

The Web flow definition file can be edited by the XML editor, and the code prompt function is also available.

The verification function of the Web flow definition file can be customized.

: Http://www.myeclipseide.com/index.php? Name = downloads & Req = viewsdownload & SID = 24

Note by the Translator:

Finally, the update of myeclipse 6.5 was introduced, although only M1. The highlight of this update is the enhancement of spring and web services, but it is not innovative. This is also the goal of this big and comprehensive full-stack IDE. Myeclipse's support for Ajax and JavaScript is also poor. I don't know that 7.0 of them will be pleasantly surprised after half a year.

Like green radish, each has its own love. One ide must have its supporters and opponents. If you are a fan of vim or Emacs or attack it only because myeclipse is a paid IDE, it is a pity, this article does not provide you with more help.

PS: The myeclipse website does not seem to be able to log on recently. The translator is Tor and finds this article. The original Article has many images and cannot be displayed. You can go to the following link to view the original article.
From: www.myeclipseide.com