For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 3 voices, and was last updated 22 years, 1 month ago by
.
-
Posts
-
Hi
Config is WinXP, Eclipse 2.1.2, Tomcat 5.0.12, MyEclipse 2.7RC2
I used previous 2.6 versions of MyEclipse and mods to a JSP worked as expected.
After installing 2.7RC2, editing a JSP in project no longer causes that page to be redeployed to Tomcat.
I can repro this behavior 100% just by creating new Web Module projects and adding a simple JSP to it.
Could it be some config I have messed up? Is there a config switch to cause hot deploy to happen, that I have missed or messed up? I think I have examined every preference setting.
I have uninstalled MyEclipse and reinstalled it from the web; same behavior.
There are two other weird behaviors that may be relevant.
1. even though I have uninstalled and reinstalled MyEclipse, and know I installed 2.7RC2, in the update & install perspective it still says version 2.6.200. And I know my MyEclipse directory completely was removed and replaced by the new install.
2. When the 2.7RC2 is installed, and I choose Help/Software Updates/New Updates, it always tells me I need to get Eclipse Project SDK (Windows) 2.1.2, which I know to be installed already. Even if i let it reinstall that, the next time I look for new updates, the same thing happens. When I uninstall MyEclipse, this behavior no longer happens.
Regards,
Hugh Winkler
Take a look at this thread and ensure that your auto-build preference is enabled.
http://www.myeclipseide.com/index.php?
name=PNphpBB2&file=viewtopic&t=747Michael
MyEclipse SupportYup, that was it… how’d that get turned off? Thanks for this pointer.
btw that version number in Install/Update perspective, that 2.6.200 sent me on a two hour wild goose chase of uninstalling and reinstalling; you guys ought to fix that next build.
And I guess I will report the other behavior, the effect that Software Updates always detects Eclipse 2.1.2 as needing update when MyEclipse is installed, as a bug.
Yup, that was it… how’d that get turned off? Thanks for this pointer.
No one really seems to know. It’s rather mysterious and has happen to me too. 🙂
btw that version number in Install/Update perspective, that 2.6.200 sent me on a two hour wild goose chase
Sorry about that. We’re reserving 2.7.0 for 2.7 GA so all the RC builds all have an interim number (2.6.n00) where n=RC number so that Eclipse will detect that a new version exists but we don’t use up 2.7.0.
And I guess I will report the other behavior, the effect that Software Updates always detects Eclipse 2.1.2 as needing update when MyEclipse is installed, as a bug.
It’s more a misunderstanding, really. 🙂 We make some mods to a couple core Eclipse plugins to enable JSP debugging. There’s a problem in the Update Manager that miscatagorizes these later plugins and warns about them. We’re working with the 3.0 team to ensure that we won’t need to make similar mods by the time 3.0 final ships.
