For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 2 voices, and was last updated 19 years, 6 months ago by
.
-
Posts
-
Not a critical one but a bug though. Please take a look at the following screenshots…
Without a HTML comment everything is ok
But with a HTML comment the ‘else’ is not beeing detected properly in the JSP expression
Hmmm, this is a fairly critical bug for an editor if you’d ask me. Although it’s probably very bad style, this would flag errors in files where one legally tries to generate comments conditionally. Now if a project lead is strict about a “no error” policy, you’d have to rewrite code because of an editor ‘quirk’.
There are quite a lot of these kind of errors lurking inside the jsp editor. I’m working on rather large J2EE projects, and I’m seeing tons of validation errors and warnings. The bad thing is that because of all the bogus warnings, it’s hard to see the warings with real meaning. (hope to have some time soon to analyze and report some more of these errorenous warnings.)
I know what you mean. This is the 3’rd Eclipse based IDE I’m “playing around” with and it’s funny in some way to see the same projects displaying always different bugs/warnings due to different editors/validation engines used…
In fact due to the bug above 3 JSP-files from one of our projects are marked “invalid” what made me wondering, since the project was never marked “invalid” before… – and all of that just because I wanted to comment out some JSP code in HTML for later use.
In the end it becomes difficult to assess which Eclipse IDE /plugin set is “better” since each seems to have it’s own strengths and weaknesses.
