Eclipse
From Resin 3.0
(Difference between revisions)
| Line 14: | Line 14: | ||
If you're starting a new project and don't need to do anything fancy, the first option is recommended, copying the configuration from the plugin. If you do need to use a custom configuration, you may need to modify it to recognize the variables that the plugin sets at runtime. The dialog box tells you what these variables are and how to set them, depending on which server profile you use. | If you're starting a new project and don't need to do anything fancy, the first option is recommended, copying the configuration from the plugin. If you do need to use a custom configuration, you may need to modify it to recognize the variables that the plugin sets at runtime. The dialog box tells you what these variables are and how to set them, depending on which server profile you use. | ||
| + | |||
| + | ==Notes== | ||
| + | Eclipse must be run with a JDK, not a JRE. | ||
==References== | ==References== | ||
* [http://blog.caucho.com/?p=228 Resin Eclipse plugin snapshot] (2009-08-18) - Blog post about using the plugin's Server configuration | * [http://blog.caucho.com/?p=228 Resin Eclipse plugin snapshot] (2009-08-18) - Blog post about using the plugin's Server configuration | ||
* [http://blog.caucho.com/?p=139 Remote deploy in Resin, Part 2] (2009-01-29) - Blog post about using host deploy | * [http://blog.caucho.com/?p=139 Remote deploy in Resin, Part 2] (2009-01-29) - Blog post about using host deploy | ||
Revision as of 18:28, 24 February 2010
The Resin Eclipse plugin is available on the Caucho Eclipse update site at http://caucho.com/eclipse. It is based on the WTP framework and features deployment modes for Resin 3.1 and 4.0.
Contents |
Deployment styles
- .war file (default) - the plugin builds a .war file of your project, then starts Resin and copies the .war to the live deploy directory.
- Temporary directory - the plugin builds a .war file of your project, then starts Resin and copies the .war to a temporary deploy directory.
- In-place - the plugin starts Resin, then points it to server your project directly out of the workspace.
- Hot-deploy - (Resin 4.0 only) the plugin builds a .war file of your project, then starts Resin and uses Resin's Git deployment functionality to deploy
Options for configuration
- The very basic configuration that's included with the plugin itself
- The configuration in the "conf" subdirectory of the Resin home
- A configuration somewhere else in the file system (e.g. /etc/resin).
If you're starting a new project and don't need to do anything fancy, the first option is recommended, copying the configuration from the plugin. If you do need to use a custom configuration, you may need to modify it to recognize the variables that the plugin sets at runtime. The dialog box tells you what these variables are and how to set them, depending on which server profile you use.
Notes
Eclipse must be run with a JDK, not a JRE.
References
- Resin Eclipse plugin snapshot (2009-08-18) - Blog post about using the plugin's Server configuration
- Remote deploy in Resin, Part 2 (2009-01-29) - Blog post about using host deploy
