For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 2 voices, and was last updated 19 years, 9 months ago by
.
-
Posts
-
After installing MyEclipse the only installation location is the path where MyEclipse is installed and I can’t change it in any dialogs where Eclipse IDE allows to select another path (for example when I install another feature)
sksoft,
I don’t quite understand what you are asking about. Are you referring to the installer or the Update Manager’s install location that is provided when you install new features? The default behavior is to use the last installed dir.OK, let’s start from the beginning. I have unpacked Eclipse 3.2.1 to C:\Programs\Eclipse.3.2.1\, downloaded JST and WST features and installed MyEclipse 5.0 GA. Now I’m trying to upgrade to 5.1 GA from local Archived Update Site, BUT… after I press Finish in Update Manager I get Duplicate Conflicts dialog:
After cancelling update process I have tryed to update only JST feature, BUT… suggested install location is C:\Program Files\MyEclipse 5.0GA\eclipse only! And I can’t change it to C:\Programs\Eclipse.3.2.1\
WHY???sksoft,
If you want to upgrade to MyEclipse 5.1, please remove JST and WST from your Eclipse install first. We are tracking an issue when installing 5.1, if JST and WST are already installed, what happens is the JSP designer and right click menus are broken because of the very slightly modified versions we ship (to support our new exclusion functionality).Also the reason the update manager is forcing you to update the MyEclipse copies is because those are the versions that have been loaded. For an update, the location is pre-determined, but when you are installing a new feature, you can select any directory you like.
Thanks for the answer, support-rkalla! You solved my problem.
But this rises another question: if someone patches some feature and releases it as the original, we always will have a duplicate conflict!
Maybe it’s better to rename it and release as a different feature? (This allows side-by-side installation other similar components)sksoft,
Yes you are right. We fixed the update site so now you should be able to update without any problems (we had forgotten to increment the version on a plugin that had changed, so what was happening is the old 5.0.1 plugin was getting loaded instead of the 5.1 version, and it was dying.)After fixing this, management has put into place a policy to avoid these issues moving forward so this shouldn’t happen again. Thanks for hanging in there, I’m glad it’s working now for you.
