[NetflixJoel]

I am having a problem with MyEclipse 5.1 (and using eclipse 3.2.2) whereby my Include files (.inc’s) are being validated and shown as all having errors. I can’t seem to get MyEclipse to not validate them without entirely disabling all JSP validation.

In Preferences -> General -> Content Types, I’ve added *.inc to the JSP Fragment type (NOTE: *.inc is also shown as being locked under top level JSP type)

In MyEclipse, the option to validate JSP fragments is Unchecked.

In Validation, JSP Syntax Validator is enabled.

When I do a clean build, it shows all my include files (inc’s) as having problems. In previous versions, MyEclipse respected the option to not validate these files. Why is it not respecting that now? Do I have some setting incorrectly set?

I can turn off JSP Syntax validator, but that is not really an option since I need that validator for all my .jsp files.

Help 🙂

THanks.

[NetflixJoel]

fwiw, I am having this problem in 5.1 and 5.5M1, but I am NOT having the problem with 5.0.1

[Riyad Kalla]

I am having a problem with MyEclipse 5.1 (and using eclipse 3.2.2)

There were some breaks in the platform when we began testing on Eclipse 3.2.2, I would suggest waiting for 5.1.1 which will be based on Eclipse 3.2.2 (due out this week).

I want to clarify, are you referring to compiler markers in the left margin or reconciler markers in the right margin? The compiler errors get added to the Problem view, but the reconciler markers are just shown in-editor and not added to any persistence state.

I created a test project here that I’m curious what you see if you download it and import it. You should only see reconciler errors in the editor and nothing persistent in the Problems view except for the “local variable is never read” warning.

[NetflixJoel]

Compiler markers. They were showing up in the left margin, as well as in the Problem view.

I will try your test project shortly.

Would you recommend a downgrade to Eclipse 3.2.1 for a quick fix?

Thanks!

[Riyad Kalla]

Joel,
It’s possible. Just to make sure that a downgrade would work, before changing you main dev environment, I would suggest you grab out 5.1.0 all-in-one installer, and install it to a test (new) location, then reopen your existing workspace and see if that did the trick.

Also, instead of downgrading you could *force* MyEclipse to ignore those files by right-clicking on them and going down to MyEclipse > Exclude from Validation. (Or doing that adjustment under project properties > MyEclipse > Validation > Excluded Resources). I’d feel more comfortable keeping you on a mostly stable base (what you have now) temporarily until our 5.1.1 release made it out the door.

[NetflixJoel]

Out of curiosity, are you sure the problem is not because, under Content Types, the *.inc is showing up locked under JSP? Even though I have added it to the list under JSP Fragments, none of the other types listed under JSP Fragments is showing up under the top level JSP. So why is *.inc? Is there a way for me to remove *.inc from the top level JSP, and have that type live only in JSP Fragments?

My problems seem to be spreading. I am using 5.1 with 3.2.1, and *.inc’s are still being validated (and obviously showing errors). Aaargh. I just want MyEclipse to ignore all *.inc’s! They are spread out through many directories, so manually excluding them is not a good option.

[Riyad Kalla]

Ok let’s try something easy and see if it works:

1) Go to File > Switch Workspace, C:\tempworkspace, hit OK to restart
2) Go to File > Import > Existing Project, be sure to check the box at the bottom about copying the project into the new workspace and import your project that is giving you problems
3) Let it build

Did it validate the INCs?

[NetflixJoel]

Yes, it did.

All .inc’s are showing up in the Problems view as having errors, and the .inc files all have the red x on them.

@support-rkalla wrote:

Ok let’s try something easy and see if it works:

1) Go to File > Switch Workspace, C:\tempworkspace, hit OK to restart
2) Go to File > Import > Existing Project, be sure to check the box at the bottom about copying the project into the new workspace and import your project that is giving you problems
3) Let it build

Did it validate the INCs?

[Riyad Kalla]

Is this project under 10mb and something you could share with me over email?

[NetflixJoel]

I wish, but unfortunately I am unable to.

Any ideas? Are you sure it is not because *.inc is listed directly under JSP in the content types? When I added it to the JSP Fragment section, is MyEclipse looking at that, or just seeing it under JSP and validating??

@support-rkalla wrote:

Is this project under 10mb and something you could share with me over email?

[Riyad Kalla]

Joel,
Can you download this project and import it into your workspace and clean it? What do you see?

On my end I see a validation error on the main JSP page because of the errror in the include (inc file) but not on the INC itself.

Also I double-checked my Content Type mappings in a clean install and oddly enough, INC is included in the “JSP” type, but not under “Fragment”…

[Riyad Kalla]

Joel,
I’m working with one of our JSP editor developers right now and I see the issue now… still working on it…

[Riyad Kalla]

This looks like it might be a bug, I’ve filed it for investigation by one of the developers.

[NetflixJoel]

I’m away from my desk, but will test that project if you still want me to.

Also, definitely seems like a bug that MyEclipse is locking *.inc as a file type under JSP. It should not include *.inc and allow users to add it either under JSP or under JSP Fragments, depending on what they want.

[Riyad Kalla]

Being under JSP I believe is correct (so it knows you can do things like scriplets, tags, taglibs, etc. and color them correctly) but it being under JSP Fragments and *still* validating it with the “Validate Fragments” setting off, seems to be the bug.

[Author]

Posts