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, 2 voices, and was last updated 22 years ago by
.
-
Posts
-
I don’t know if this is an eclipe or a MyEclipseIDE issue, but anyway here it is.
When I build a project, different problems are listed in the problems view, according to the warning levels I set under preferences – Java – Compiler. So far so good.
When I recently upgraded from the last eclipse milestone build+ME 3.8rc1 to eclipse 3.0+ME 3.8rc2, the problems view suddenly started to report thousands of problems in my JSP files, like e.g.
– ‘Unnecessary cast to type boolean for expression of type boolean’
– ‘The type FormActions is deprecated’
– etc…..So what has apparently started to happen is that also problems inside of the JSP taglibs I use (like e.g. Struts 1.1 taglibs) is reported.
So to my question to the forum:
– Can this behaviour be disabled / turned off?IIRC these are handled by lowering the problems that your compiler settings reports. Right click on your project and check out your compiler settings, you can set it to IGNORE these less important errors.
@support-rkalla wrote:
IIRC these are handled by lowering the problems that your compiler settings reports. Right click on your project and check out your compiler settings, you can set it to IGNORE these less important errors.
IIRC?
Well, of course I could do this, and it is what I have done temporarily. My Workaround is to turn it on each time I want to have these kinds of potential problems reported. The drawback is that a full rebuild is needed each time I change these settings.
But the problem is this:
1.
– I want to have these checks ENABLED for all my Java code.
– I don’t want my JSP taglibs or other libraries validated, since I have no control over their contents anyway.
2.
– Before I upgraded eclipse+MyEclipse this was not a problem
– Since I upgraded both at the same time, I do not know which program caused this behaviour.1) I understand your position, and we have filed/fixed 5 or 6 of the erroneous warnings so they shouldn’t be reported anymore in the new build. The problem was partly due to the servlet that was internally getting generated from the JSP page had unnecessary casts and such in it, so 3.8 GA should fix this. You can also play with your filter settings to try and filter out the extra warnings.
2) It is likely a combination of both, 1 Eclipse offering more control of what to warn you about and 2 MyEclipse generating code that is triggering those warnings.
