• m2eclipse compatability

• reverse engineering, validation, auto completion

• JSDT integration
• JS closures/OOP
• Enhanced editing
• Code browsing

• UML 2 diagrams
• Property editors and validation
  

• BIRT 2.3 support
• JavaScript/scripting improvements
• Crosstab enhancements
• Multi-view items
• Chart improvements
• more!

• Editor views
• EL improvements
• Apache Trinidad support

Maven4MyEclipse now offers full compatibility with m2eclipse Maven projects, and will optionally work as an m2eclipse plugin, by enabling this option within the preference page.

It conveniently defaults to disabled, to prevent MyEclipse users from un-wittingly creating projects which do not conform to MyEclipse project configurations.

MyEclipse Standard Edition users cannot utilize Professional Edition Maven features such as Maven4MyEclipse project creation, but are now allowed full access to the m2eclipse plugin.

MyEclipse 7 Milestone 2 includes OpenJPA as a persistence provider. You can now select OpenJPA when you add JPA capabilities to your project.

Create a persistence unit easily using existing connection details.

Here is an example of a generated persistence.xml file.

OpenJPA 1.2 libraries are added to your project when OpenJPA is selected as a persistence provider.

These libraries can be customized on the JPA preference page.

Existing JPA features such as reverse engineering, validation, auto completion, etc., remain available for OpenJPA persistence projects.

MyEclipse 7 Milestone 1 delivers a superior JavaScript editing experience to MyEclipse, including features like OOP awareness, code folding, improved content assist, code templates and much more.

To get a better idea of the OOP support, compare the Outline view for the same JavaScript file in both MyEclipse 6.5 and MyEclipse 7 Milestone 1.

MyEclipse 6.5

MyEclipse 7 Milestone 1

This improved model translates to improved content assist and navigation capabilities across your project. Your project's global scope can be extended by adding predefined libraries to your project and / or adding JavaScript files and folders to the scope. Objects, fields and methods defined in these files will be provided as options for content assist even when you may be editing another JavaScript file. 




Adding a library to your environment


Adding JavaScript source to your environment

Text is indented as you type, braces and parenthesis are automatically closed.

Code Templates insert snippets of commonly used JavaScript constructs into the editor.

With Code folding, browsing large and complex JavaScript files is easier.

Use the Clean Up wizard to apply coding style preferences to your JavaScript source.

Content assist proposals will also display Jsdoc if available. Just like the Javadoc view, the Jsdoc view will display the Jsdoc for the current element.

The outline view now presents a more accurate picture of your source. You can also use the quick outline (Ctrl + O) to navigate to fields and methods within the file being edited.

Hyperlink navigation is also possible, simply press Ctrl and click a variable or method to be taken to the declaration.

Use the Javascript search to find elements of interest.

The JavaScript perspective includes the Script Explorer view which presents a JavaScript centric view of your project. The JavaScript model is also displayed in the Project Explorer. Simply double click an element to be taken to that location.

The new Quick Edit tab in the property view allows structured editing of JSF tags.

The Component Tree view presents a design time approximation of your JSF views.

Improved EL content assist.

Hyperlink navigation is now available in the source page; Ctrl + Click on a Managed Bean variable, property or method referenced in the EL of an attribute to navigate to that location.

Improved EL hover help.

Support for Trinidad tags is available in the Design/Source panes and in the Property view.

MyEclipse 7 introduces early support for drawing in UML 2 - such as the drawings below. These capabilities will continue to evolve, to match the more complete UML capbilities currently found in our long standing UML1 feature set. An example of capablities still to come is the two-way code/UML generation that is currently in our UML1 feature set.

Our UML 2 editor allows you to create and edit nine different types of UML 2 diagrams.

Class Diagram

Component Diagram

Deployment Diagram

Composite Structure Diagram

Use Case Diagram

Activity Diagram

Sequence Diagram

State Machine Diagram

Profile Diagram

Outline View
Use the outline view to easily navigate the diagram, graphically or structurally.

Selecting an existing element allows you to further modify it in a tabbed property view. A few properties are shown below.

Parameter Properties

Advanced Properties

Use the validation action to validate your UML 2 model. Errors and warnings will be displayed in the diagram, Outline and Problems view.

The UML 2 editor toolbar contains all the features you need to create visually appealing diagrams. The ability to automatically layout diagrams aesthetically will be added shortly.

Further control is possible through an element's context menu and the Graphics tab in the Properties view.

Graphics Property Tab

Use the UML 2 preferences to specify the default styling for UML 2 entities.

MyEclipse Reports has been upgraded and now integrates BIRT 2.3, a major update from version 2.2.0 used by MyEclipse 6.5. There are enhancements across the board, from better scripting and JavaScript capabilities to core reporting improvements in features like Crosstab and the addition of Multi View reports.

MyEclipse Reports offers many enhancements to the JavaScript editor (available in the Scripts page of the Report editor) including code folding and script validation. The automatic validation feature will help with the development of JavaScript event handlers, allowing some code errors to be discovered prior to the execution of the report.

In addition to automatic JavaScript validation within the JavaScript editor, a validate button within the Expression Builder will verify the JavaScript syntax used within a BIRT expression.

Several report elements have been enhanced to support additional event triggers. The cross tab element now supports onPrepare, onCreate, and onRender events for the cross tab and for each cell within the cross tab. Using these new events the rendered cross tab element can be altered in many ways. The following screenshot illustrates a script that alters the cross tab element in its onPrepare method and alters the individual cell element instances based on data within the cross tab.

In addition to the new events for the cross tab element, chart scripting has been improved to support beforeDrawMarker and afterDrawMarker events. Using these events the individual markers for the chart and legend can be altered.

Filters, which cull the data displayed in the cross table, can now be applied to measures. In prior releases, filters could only be applied to the dimensions.


In this example, the amount measure is filtered to only show values over 50,000, which results in the following cross table output. Report elements are alsoe placed in the cross table header.

Measures represent the intersection point for the column and row values and are by default displayed as an alphanumeric value, these values can now be displayed graphically.

Individual charts can be displayed for each measure and can be generated against the vertical or horizontal dimension. Charts can also be used for cells containing total elements.

Cross tab elements now support derived measures. These can be created by using the Derived Measure dialog, which is launched with the menu context item “Add Derived Measure”. The BIRT Expression builder is used to construct these derived measures and all cross tab bound items are available for use within the expression.

Report items can have multiple views, wherein all views share the same data, filtering, and grouping. The view of the data determines how it is to be displayed and is essentially just another report item sharing the same graphical space and bound data. Currently only tables and cross tables support this feature and the secondary view must be a chart. The view displayed of the data can be selected using the view tab at the bottom of the report element.

Some of the improvements are explained in the sections above, which describe multi-view report item support for tables and cross tables. In addition, grouping and sorting for charts has been improved. In previous releases, categories and optional Y series grouping were available, but sorting these groups could not be done with a separate data value. With this release, a sort on field has been added to both the category and optional Y series grouping dialogs. Many new grouping unit types are also available, including quarters for date time fields. The interval for numeric data types can now be set to a decimal value.

Charts, embedded in reports, can now consume data from report cubes. This is in addition to the existing support for data sets and report items.

External Style Sheets
In prior versions, if using a linked style sheet, the css file had to be located in the resource folder for the given project. Now you can link the style sheet at view time, and it can be referenced as a full or relative URL.

Horizontal Page Break Support
To use this feature, within a table select the column(s) you wish a page break to occur and navigate to the Page Break field in the Properties View. Then select “Always” either for the “Before” or “After” setting. This setting will instruct the report engine to insert a page break at that column. To configure this setting for a crosstab element, select the crosstab and navigate to the Column Area tab, then select the Page Break field and add the appropriate page break setting. Illustrated below is an example of setting the horizontal page break for a table.

Copy and Paste Formatting The formatting specified for a report element can be copied to another report element.

Library Changes The Library Explorer View supports multiple enhancements, including navigating all resources within the specific resource folder. These include images, scripts, jars and libraries that located in the resource folder. Many UI changes have also been made to facilitate better resource management. These changes include the ability to add or create new content within the resource folder using an improved context menu. In addition, adding content to libraries has been improved; any report element can be published to a library by using the context menu.