Community
Participate
Working Groups
preferably the validation would be managed the same as other validators, such as XML and HTML
Steffen, it would be nice to leverage the WST validation API for this purpose. In doing so we get automatic integration into the configuration UI for validators. The downside of such integration includes: # a new build dependency # validation would only run if the user had WST installed I'm okay with the 2nd issue, however the new plug-in dependency may be problematic. Not only is WST a heavyweight, @org.eclipse.wst.validation.AbstractValidator@ is javadoc'd as provisional API. What are your thoughts?
Created attachment 118607 [details] initial implementation of WST validation
Created attachment 118608 [details] mylyn/context/zip
That seems like a great idea. I wouldn't worry about the provisional APIs, I think it's hard to implement anything based on webtools that doesn't use internals. The build dependency might be okay but we should discuss that on a conference call. How much harder would it be to implement a custom builder for the markup validation to avoid a dependency on webtools?
(In reply to comment #4) > The build dependency might be okay but we should discuss that on a > conference call. Sounds good > How much harder would it be to implement a custom builder for > the markup validation to avoid a dependency on webtools? It's not hard at all. The downside is that we won't get the GUI for enabling/disabling validators.
I've put some thought into this one. Perhaps it would be good to have both builders. That way everyone would get validation, and those that have Web Tools installed would get the UI. Of course, only one builder would be enabled at any given point in time. In the short term until we get the build dependencies issue sorted (in part, bug 256510) a simple non-WST builder would do.
Turns out that the UI is pretty important. Without the UI there is no way for a user to associate the validation builder with the project. Adding the builder can be done by editing the .project file, but that's a non-starter. The WST plug-ins add settings for Validation under the project properties. For WikiText to do the same is senseless. Perhaps it makes sense to have a @org.eclipse.mylyn.wikitext.ui.wst@ plug-in to separate the dependencies as proposed in bug 256510.
Use non-WST builder Create a new WikiText project nature that automatically adds the builder. * prompt to add nature if it doesn't exist if a wikitext file is created, with don't ask me again option * always add the nature with builder disabled if a wikitext file exists in the project?
An incremental project builder has been implemented. See the Mylyn WikiText User Guide for details.
Created attachment 119926 [details] mylyn/context/zip
