There will be no more versions of Struts Plugin for two simple reasons:
a) no more time
b) Struts Assistant comes now pre-packaged with IDEA 6.0
I have joined Dmitry Avdeev (JetBrains) to continue the development of Struts Assistant to make it more powerful (and add some of the features from Struts Plugin I'm still missing :-)). Look forward to lots of enhancements and feel free to put your requests on JIRA.
Some people experienced problems when upgrading to 5.1 and taking over their old configuration and plugin versions: IDEA wouldn't start anymore with an old (5.0.x) version of Struts Plugin.
Please follow the instructions in the Knowledge Base to deinstall the old version first, then install the latest version via plugin manager.
Sorry for the inconvenience, but there were many internal changes in IDEA 
This is the homepage of Struts Plugin, the most downloaded plugin to support the development of Struts based web applications within IDEA 5.x.
Read the latest news on my blog "Struts, IDEA and such".
Please visit StrutsPluginsFeaturesOverview to see a feature comparison table of all Struts plugins available for IntelliJ IDEA.
IDEA 5.1
(bugfixes only)
V0.89d for IDEA 5.1/5.1.1 (build #4155 or higher)
IDEA 5.x
(stalled, no further development)
V0.82 for IDEA 5.0.2
SP = Struts Plugin
Open IDEA's plugin manager and download SP. Restart IDEA and open "Settings" to verify SP is installed (icon in "Project Settings"). If you have StrutsAssistant or StrutsNavigator installed you will be warned about problems (SP won't work properly if any of the two is installed simultaneously and vice versa).
There's a couple of rules/configuration steps to enable SP to work correctly with your project. Most existing project will work without any further changes, but here's a checklist if you encounter any problems:
Make sure your web module is configured properly, that is:
- web.xml listed in Deployment Descriptors and valid
- struts.jar must be present in any library path (ofcourse!
 )
- web resource directories must be mapped correctly with corresponding relative deployment path
- Settings dialog displays a tree-like overview of all auto-discovered configuration files, make sure all your config files show up and check the following points if they don't
- must contain a valid and registered <!DOCTYPE> declaration STRUTS PLUGIN WON'T RECOGNIZE THEM OTHERWISE you can lookup the correct ones in your Struts distribution in folder /lib/ (search for the corresponding DTD and then in its header comment)
- can be located anywhere in your project - as long as the containing directory is correctly mapped to a relative path for deployment
- SP will automatically find all related configuration files as long as you follow the rules above (which you should do, anyway)
- separate multiple struts-config.xml files in your web.xml's ActionServlet? declaration by ","
- struts-config.xml must contain a plugin definition for TilesPlugin? (or subclass) pointing to tiles-defs.xml file(s) (multiple files separated by ",")
- configuration via ActionServlet?-parameters in web.xml is considered deprecated and not supported
Navigation Support in JSPs
- navigation will only work in conjunction with "original" Struts(-EL)-HTML tags, there's no support (yet) for custom tags overriding the original Struts tags
- use the original TLD-files (if mapping them manually in your web.xml)
Please read the Tips available from menu "Help->Productivity Guide" in Group "Struts Plugin".
If you have any specific questions/problems feel free to mail me directly, mail-address is listed in IDEAs plugin manager.
The full changelog is available here.
-- YannCebron - 27 Oct 2006
|
|
