- This topic has 7 replies, 3 voices, and was last updated 19 years, 8 months ago by
.
-
Posts
-
THe way I’ve always done it, is instead of inlcluding the BODY tag in every page, I would <@% include file=”header.jsp” %> for every page.
Now eclipse is giving me 100s of warnings for every single page that there’s no starting and no ending body tag.
How can I get it to shut up?
But what if I don’t want to turn off the entire validation? Just certain aspects? Do I get the finger? 🙂
Well, technically, the file IS HTML compliant. It’s just that the compliance is located inside the <%@include %>.
I don’t think it would be such a hard task to extend the validation process to the static includes…
WHat you say?
We agree with you, it is just a very low priority behind some more pressing features we have on our todo list. Having a balancing act between all these feature requests that are a “must have” for every one of our users is not an easy task, something has to give.
May I ask where I can look at what the current priorities are? Because it seems anything that I say is a low priority 🙂
I don’t think it would be such a hard task to extend the validation process to the static includes…
The fact that includes are not expanded in the validation process at this time is that the problem is harder than it appears to the casual observer, especially with in the Eclipse edit framework. Presently the validator does not yet have a configuration warning/error filtering mechanism (but we are considering it post-ME 4.0).
Regarding priorities we have a big push for ME 4.0. You can read about the feature-set here: http://www.myeclipseide.com/displayarticle37.html Features planned beyond ME 4.0 will necessitate serious extension of the Eclipse editor framework. That will be the most optimal opportunity to address this family of problems.
As Riyad indicated earlier the near-term solution is to either disable validation or refactor the include.
