Yes - I think we should base it on the WTP validator. We still need the new project wizard that adds the WTP validator as a builder to the project, and optionally adds the Java nature for it to work properly.
----- Original Message ----
From: Jesper Steen Møller <jesper@xxxxxxxxxxxxx>
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Sent: Wednesday, 19 December, 2007 10:50:23 PM
Subject: [wtp-incubator-dev] XSL checking as "nature + builder" vs "WTP validator"
Hi guys
I'm porting over the validation + UI portions of the X-Assist plugins,
adding some validation tricks as I go.
We've previously discussed whether to use a XSL validator or a specific
XSL project nature with a builder.
In light of the new validation framework to appear in the next major WTP
[1] I think it would make the most sense to stick with the "WTP
validation" direction, primarily because it makes the XSL support work
"out of the box" and in a less intrusive manner.
In fact, I'd rather do it this way, and then in return help out
on the
validation UI stuff to make it on par with the user experience of the
Java tooling, as suggested by Dave.
I should be able to make it backwards compatible with the current WTP
2.0 as well.
Comments anyone?
-Jesper
[1]:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=212196_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev