| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="ISO-8859-1"> | |
| <title>New and Noteworthy for Eclipse Tools for Cloud Foundry, 1.0.2 (Neon.2)</title> | |
| </head> | |
| <body> | |
| <h1>New and Noteworthy for Eclipse Tools for Cloud Foundry, 1.0.2 (Neon.2)</h1> | |
| <h2>General</h2> | |
| Eclipse Tools for Cloud Foundry (CFT) 1.0.2 contains various bug fixes and framework enhancements. | |
| <h2>Improvements</h2> | |
| A couple of general and usability improvements have been introduced in this release: | |
| <ul> | |
| <li> | |
| <b>Missing service detection on Services Selection page</b> | |
| <p>The Services Selection page in the application deployment wizard now detects if a service instance for a service binding in the manifest.yml of an application does not exist when deploying an application. It also provides suggestion to guide you how to resolve the problems.</p> | |
| <p> | |
| <img width=442 height=360 src="images/MissingServices.png"> | |
| </p> | |
| </li> | |
| <li> | |
| <b>Module out of sync detection during application deployment</b> | |
| <p>A more informative error is displayed when the server is out of sync with the Cloud for unpublished (not deployed) modules. If a module fails to deploy correctly and the actual application in the Cloud is not created, yet the module still exists in the server, CFT will detect the server as being be out of sync with the actual Cloud. Previously, CFT would show a cryptic error in such cases. The tools will now detect if the server is out of sync and provide better instructions on the steps to fix the issue.</p> | |
| <p> | |
| <img width=624 height=150 src="images/ModuleOutOfSync.png"> | |
| </p> | |
| </li> | |
| <li> | |
| <b>Child modules publish improvement</b> | |
| <p>Existing published parent modules are now correctly re-published when new child modules are added. This framework fix allows tools that extend CFT and support projects with child modules, like Enterprise Application Project (EAR), to correctly support re-publish scenarios any time child modules are added to an already published parent module. | |
| </p> | |
| </li> | |
| <li> | |
| <b>Lower case URL on suggested deployment URL</b> | |
| <p>Upper case in generated application URLs in the application deployment wizard are now converted to lower case for certain cases. This is to address a bug in the URL generation mechanism (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=502070">bug 502070</a>). Vendors that contribute a server branding through the CFT branding extension point now have the option to switch to generating application URLs with only lowercase by adding the following attribute to their extension point definition, and setting the value <i>supportUpperCaseURL</i> to false. | |
| </p> | |
| <p>Example:</p> | |
| <p> | |
| <code> | |
| <DL><extension | |
| <DD>point="org.eclipse.cft.server.core.branding"> | |
| <DD><service | |
| <DD> name="Pivotal Web Services" | |
| <DD> provideServices="true" | |
| <DD> remoteSystemTypeId="org.cloudfoundry.cloudfoundryserver" | |
| <DD> serverDisplayName="Pivotal Web Services" | |
| <DD> serverTypeId="org.cloudfoundry.appcloudserver.10" | |
| <DD> supportUpperCaseURL="false"> | |
| <DD></service> | |
| <DT></extension> | |
| </DL> | |
| </code> | |
| </p> | |
| </li> | |
| <li><b>Other improvements include:</b> | |
| <p/> | |
| <ul> | |
| <li>Many bug fixes and tool stability improvements</li> | |
| </ul> | |
| </li> | |
| </ul> | |
| </body> | |
| </html> |