Fuse IDE v2.1 runs on Eclipse v 3.7 and works with m2e, the new Maven integration in Eclipse.

Using the Installer, you can now download the full binary distribution, which includes Eclipse v3.7.

	Tip
	You can still use the Eclipse plugin update mechanism to download Fuse IDE v2.1. If you do so, make sure you are running Eclipse v3.7; otherwise, Fuse IDE v2.1 will not run.

The Fuse Fabric perspective is the staging area for connecting to and managing fabrics. A fabric created by Fuse Fabric technology is a cluster of containers, each of which has an associated profile (and version) that determines what runs inside it. You can view, create, edit, and delete fabric details (connections to existing fabrics) and profiles; create and provision containers; and create versions. You can navigate fabrics to see their underlying JVMs. Open a terminal on any process in a fabric to have full Fuse ESB console access with colors and tab completion, without having to remember host/port names. Easily browse JMX, Fuse MQ, and Fuse ESB beans, endpoints, routes, and so on, without having to remember JMX URLs.

If using a JClouds-supported cloud provider (EC2, Rackspace, Slicehost, VMware, vSphere, ...), you can create, view, pause, resume, and reboot your compute nodes directly from Fuse IDE, and you can easily find and view all logs distributed across multiple fabrics.

You can now export your route diagrams as PNG, JPG, or BMP files to easily include them in presentations or documentation.

The route editor displays only one route on the canvas at a time, so the Route box has been eliminated. Now you can freely move nodes around as you add more patterns to the canvas. Fuse IDE provides an easy mechanism, Outline view, for switching routes on the canvas. You can also switch between routes using the Routes menu on the menu bar.

The route editor's connector tool is now part of each node on the canvas. Simply hover the mouse over a node to reveal its connector arrow, then drag and drop it on a target node to connect the two nodes.

Connectors now have bendpoints that break them into segments, enabling you to easily drag connectors around densely packed nodes in complex routes.

Beans and endpoints defined in the routing context file are added to the Endpoints group in the Palette, so they also appear in the Routes menu and the context menu's Add > Endpoints submenu.

Two-finger trackpad scrolling on the canvas has been improved.

The Fuse IDE perspective has been renamed Fuse Integration to more clearly indicate its function.

Visualizations of endpoints, routes, processors, queues, and topics have been combined with tables and charts, so you can easily see relative sizes.

For route tracing, profiling and timing metrics have been added to both the Messages view and the Diagram view. Profiling identifies which steps in a route were invoked the most times and which steps took the most time to process messages. Timing metrics displayed in Diagram view include average time, count, max time, and min time.

You can now easily adjust the order and width of the columns in all tabular views. To rearrange column order, you simply drag column headers to different locations in the table. To resize column width, you simply drag a column's boundary line to expand or contract the width. To hide a column from view, you simply contract its width completely.

Fuse IDE now provides JVM statistics views on JMX Explorer, so you can see MBeans, Timeline, Threads, Memory, and CPU statistics.

Fuse IDE cannot be installed into Spring STS eclipse distributions because Fuse IDE uses m2e, while Spring uses m2eclipse.

Slated to become functional in v2.2.

Once you've create a child container in a fabric, to delete it, you must issue the fabric:container-delete <containerName> command from the Fuse Fabric console command line. Slated to be fixed in v2.2.

In Design view, you can connect any node with any other, regardless of whether the connection between the nodes is valid. In v2.0, the route editor did not permit connection between invalid pairs of nodes. The arrow end of the connector displayed a red error icon, and the connector failed to stick to the target node. In addition, the nodes' context menu's Add option presented only the patterns that could validly connect to the selected node. This behavior is missing in v2.1.

Slated to be fixed in v2.2.