- This topic has 4 replies, 2 voices, and was last updated 16 years ago by Riyad Kalla.
-
AuthorPosts
-
kldavis4MemberI am using MyEclipse 7.0-M2-20080915 with a web project with many html/jsp pages. If I allow validation to complete, it takes a LONG time. I have the directory where these files are sitting in the Excluded Resources list, but it is still validating them. Please advise.
<VENT>This is extremely frustrating. I have been a subscriber for years now, and throughout that entire time the web development stuff has pretty much sucked. The JSP editing/validation has been buggy and slow. The web hot deployment regularly breaks for seemingly inexplicable reasons. The most frustrating thing is that all of the alternatives I have tried are inferior in some other aspects and I am pretty much forced to use MyEclipse. I know part of the issue here is that I have a very large (legacy) project with lots of very large jsps, and you guys probably don’t test for this kind of thing, but something needs to happen on this front because eventually someone is going to implement something that works better and you are going to get dropped.</VENT>
Riyad KallaMemberI am using MyEclipse 7.0-M2-20080915 with a web project with many html/jsp pages. If I allow validation to complete, it takes a LONG time. I have the directory where these files are sitting in the Excluded Resources list, but it is still validating them. Please advise.
Thank you for bringing this to our attention, it looks like the directory-filtering was broken during that Milestone, it will be fixed in 7.0 GA. The workaround right now is to exclude the *specific* resources, it might be faster to do this from the Project Properties > MyEclipse > Validation > Exclude dialog.
As far as the VENT, the bottom line is that our users shouldn’t feel like this; that’s a shortcoming on our part that we need to rectify. User experience and general user happiness is something we’ve been discussing a lot of lately; figuring out how best to balance both our time addressing new features and fixing existing bugs is something we are in the middle of streamlining to improve this going forward.
One change that is being made effective immediately is that we are moving back to quarterly releases. We tried doing longer-cycled major and shorter-cycle feature-specific releases and the reaction from our users is that overall it didn’t really help them out and if anything I think was more confusing (e.g. logging in and seeing a big update for Matisse4MyEclipse, but not a MyEclipse upgrade).
7.0 will include the software foundation for us to streamline our releases and updates moving forward along with tight/focused schedules for 7.1, 7.5 and 8.0 to come all probably in ’09; each one including releases and bug fixes across the board most tightly tied to what our users are demanding.
We are also going to allow people to piece-out parts of MyEclipse they aren’t using that often to improve overall IDE performance, and allow adding/removing/toggling of the IDE pieces at-will.
Thank you for taking the time to let us know about the issues you are running into; keep us honest, let us know you are mad. We have to earn your business and if we aren’t doing a good job at that, we’ll make a course correction to be sure we do.
Riyad KallaMemberJust a heads up, we got this fixed for 7.0 GA which should be out next week.
kldavis4MemberRiyad, Thank you for the quick response (and fix) and for thoughtfully addressing my complaints. I will look for the new release. Kelly
Riyad KallaMemberKelly, not a problem. We’ve all been users of different pieces of software out there and we *want* to fix everyone’s bugs or feature requests, it’s just a tricky balancing act.
Luckily you caught me on a Monday, and I agree to everything on a Monday 😉
(That’s a joke btw, incase anyone reading this decides to queue up a huge laundry list for next Monday)
-
AuthorPosts