| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="ISO-8859-1"> | |
| <title>New and Noteworthy for Eclipse Tools for Cloud Foundry, 1.0.1 (Neon.1)</title> | |
| </head> | |
| <body> | |
| <h1>New and Noteworthy for Eclipse Tools for Cloud Foundry, 1.0.1 (Neon.1)</h1> | |
| <h2>General</h2> | |
| Eclipse Tools for Cloud Foundry (CFT) 1.0.1 features a new authentication support, various improvements to the user experience, a new feature and enhancements to the framework. | |
| <h2>Improvements</h2> | |
| A couple of general and usability improvements have been introduced in this release: | |
| <ul> | |
| <li> | |
| <b>Single sign-on (SSO) support</b> | |
| <p>CFT now supports single sign-on (SSO)/passcode when creating a Cloud Foundry server instance. In the New Server Wizard, when selecting a Cloud Foundry server type, a new UI in the <b><i>Account Information</i></b> section allows users to specify a passcode instead of username and password. A link has been added to provide the server specific single sign-on link to generate the passcode. Users can also switch from passcode to username and password UI using a checkbox. | |
| </p> | |
| <p> | |
| <img width=442 height=479 src="images/SSO.png"> | |
| </p> | |
| </li> | |
| <li> | |
| <b>Server state display on server editor</b> | |
| <p>Applications section in Cloud Foundry server editor now shows running state like in the Servers view.</p> | |
| <p> | |
| <img width=624 height=180 src="images/applicationState.png"> | |
| </p> | |
| </li> | |
| <li> | |
| <b>Application deployment framework improvements</b> | |
| <p>The CFT Application Delegate framework has improvements that now allow multiple application delegates that provide application archiving mechanisms to be registered for the same module type. These changes are primarily intended for tool developers extending CFT, rather than actual CFT users.</p> | |
| <p>With the new framework changes, CFT will check all registered archiving mechanisms when archiving an application for Cloud Foundry deployment, in the priority order that they were registered, until it finds one that can archive the application prior to deployment. Previously only one archiving mechanism per module type was supported through CFT extension points.</p> | |
| </li> | |
| <li><b>Other improvements include:</b> | |
| <p/> | |
| <ul> | |
| <li>Many bug fixes and tool stability improvements</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| </body> | |
| </html> |