- This topic has 12 replies, 3 voices, and was last updated 20 years, 1 month ago by Riyad Kalla.
-
AuthorPosts
-
madcoderMemberWhat is the proper way to upgrade my struts 1.1 project to a struts 1.2 project?
Riyad KallaMemberThe easiest way to do this is to create a new Web Project, add Struts 1.2 capabilities to it and then drag-drop (COPY) your existing project over ontop of the new one (files and folders, but probably not the libs and tlds as yo uwould want the new ones from the Struts 1.2 release). Then deploy and make sure your project works and close your old project.
Another way I find works for me, but another user mentioned it did not work is to:
1) Remove web capabilities from the project
2) Re add web capabilities
3) Re add Struts 1.2 capabilitiesI’ve done this twice and it has worked for me, but you might want to backup your project (export to a zip or something) incase this doesn’t work.
madcoderMemberI just tried creating a NEW project using struts 1.2 and when i go to the myeclipse-struts properties a get an error. the currently displayed page contains invalid values. I have myeclipse 3.8.3 and eclipse 3.0.1.
any ideas?
thanks
Riyad KallaMemberAhh, its a bug we are going to fix in the next quickfix release. Its harmless and the only editable value on that page is the default package to use for code generation. As a workaround (a not-so-good-one) you can open the .mystrutsdata file using the navigator view and the default Text Editor manually and just change the package value in there if you need to. Sorry for the inconvenience.
madcoderMemberThanks…yes. I saw that the only difference was that the strutsVersion was a 2. Changing that back to a 1 fixed the problem.
Are there plans to create a library set for the struts jars?
madcoderMemberBTW…thanks for the help.
When is that quick fix due?
Riyad KallaMemberAre there plans to create a library set for the struts jars?
Right now our project capabilities are bound to lists of resources that are added to a project. Later on we may change this to relate to prepackaged library sets. Right now it isn’t on the TODO list, but could be soon… its just a resource allocation issue.
When is that quick fix due?
No ETA yet, January some time I imagine.
madcoderMemberWould be cool if we can create our own library sets. I like the fact that I can configure them.
Riyad KallaMemberWould be cool if we can create our own library sets
You can, they are called User Libraries. A lot of people using MyEclipse like to preconfigure their own libraries (Struts, Hibernate, J2EE, Servlet, etc.) and attach all the docs and source to them and then add that custom User Library to all their projects that require it. That is why we added deployment of USer Libraries to the 3.8.3 release, because a lot of people were doing this and needed those libraries to be deployed with their projects.
You can get to the User Libraries by navigating to Window > Prefs > Java > Build Path > User LIbraries.
madcoderMemberCool! Thanks!
Riyad KallaMemberNo problem.
kbottnerMemberUpgrading using the method of removing WebProject Capabilities and then adding them back in, followed by the corresponding addition of Struts 1.2. I do have the same error with viewing the MyEclipse-Struts properties page.
I would like to add this is even a bigger pain if you project is using Source Control. I request the addition of a simple method of upgrading from one version to the next. You have all done such a great job everywhere else, I am sure this will be a small matter.
Thanks!
Riyad KallaMemberUpgrading using the method of removing WebProject Capabilities and then adding them back in, followed by the corresponding addition of Struts 1.2. I do have the same error with viewing the MyEclipse-Struts properties page.
As madcoder mentioned it was just an oversight on our part. You can adjust the value in your .mystrutsdata file as he mentioned to work around it for now.
I would like to add this is even a bigger pain if you project is using Source Control.
Why is that? I imagine creating a new project as my first suggestion would be the biggest pain for a project under source control, but removing web caps and rolling them back in only changes your project files (assuming you have them under source control) and naturally adding new version of Struts would overwrite all the lib versions… other than that I’m not sure why this would cause you unnecessary pain?
I request the addition of a simple method of upgrading from one version to the next.
Can you outline how you would want the feature implemented? What steps would you like to take to upgrade a project’s capabilities? (so we get an idea of what our users expected).
-
AuthorPosts