Cloud Foundry Integration for Eclipse allows users to deploy applications to Cloud Foundry targets from either Eclipse IDE JEE Indigo or STS (SpringSource Tool Suite) 2.9.0 or higher.
Cloud Foundry Integration for Eclipse 1.0 is the first version of the integration to be open sourced under the Eclipse Public License (EPL), and cannot be upgraded from earlier versions of Cloud Foundry Integration for Eclipse. Users wishing to install it must first uninstall any prior version of Cloud Foundry Integration for Eclipse.
Detailed steps on how to install the Cloud Foundry Integration for Eclipse can be found at:
http://start.cloudfoundry.com/tools/STS/configuring-STS.html
After installing the Cloud Foundry Integration for Eclipse, a Cloud Foundry target must first be created through the Eclipse New Server wizard, and URL and account information for either the public cloud (i.e., CloudFoundry.com) or your local cloud target needs to be specified. Create an account on CloudFoundry.com to deploy applications by going to:
https://my.cloudfoundry.com/signup
For debugging support, users are encouraged to obtain Micro Cloud Foundry from:
https://my.cloudfoundry.com/micro
Once a Cloud Foundry target is created, it appears in the Eclipse Servers view, and users can deploy applications simply by dragging and dropping them from the Project Explorer into the Cloud Foundry target.
During the drag and drop deployment, a wizard allows a user to set application details like memory limit, mapped application URL, and optionally, also bind Cloud Foundry services like MySQL and vFabric Postgres databases, or RabbitMQ messaging to the application. In addition, users can select whether to automatically start the application after deployment, or even debug it if deploying it to Micro Cloud Foundry that supports debugging.
After deployment, users can continue to edit application deployment details in the Applications tab of the Cloud Foundry server editor, which can be opened by double-clicking a Cloud Foundry target in the Servers view.
Additional services can be created and bound to the application. Services available in the Cloud Foundry target are listed under the Services pane, and can be dragged and dropped onto the Application Services pane to bind them to a specific application deployed in that target. Furthermore, applications can be stopped, and updated and restarted through editor controls. Update and Restart allows users to incrementally publish local changes in an application without having to manually stop or redeploy the application.
Java debugging can be enabled via the editor for Micro Cloud Foundry, which provides support for debugging. Users can restart applications in either debug or run mode, as well as connect applications already running in debug mode to the Eclipse debugger, if the application wasn’t already connected to the debugger.
Cloud Foundry Integration for Eclipse is fully integrated into Eclipse debugging functionality, and applications deployed to Micro Cloud Foundry with debug support can be debugged the same way as if they were debugged locally. Users can set break points, step through code, and suspend applications through the Eclipse Debug perspective.
Users can also view deployed Cloud Foundry resources through a Remote Systems View, including configuration and log files.
We welcome any questions or comments at:
http://support.cloudfoundry.com/
For developers, Cloud Foundry Integration for Eclipse is available at github:
https://github.com/SpringSource/eclipse-integration-cloudfoundry
In addition, we encourage users to raise any issues or suggest enhancements at:
https://issuetracker.springsource.com/browse/STS
Issues can be raised under the “Cloud Foundry” component in the STS project.
-The Cloud Foundry Team
Don’t have a Cloud Foundry account yet? Sign up for free today
About the Author
