I presume that we need to vote on stuff like this.
Is that so? Anyway here goes ...

The experimental build target './build.sh validate-config'
is working nicely to validate important core configuration
files. It is currently processing these ...
* all book.xml instances
* all cocoon.roles instances
* all stylesheets (yes all 219 *.xsl)
* all sitemap.xmap instances (but not any other *.xmap)

I reckon that it should be called by default during the
build. This would mean calling the target from elsewhere
early in the process. The user can switch it all off via
properties.xml

So, let us vote ...

[+1] Call 'validate-config' by default during the build.


Here is the proposal thread if you need it:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103595545802339

---------------------------
> From: David Crossley
> To: cocoon-dev
> Subject: [PROPOSAL] build-time XML validation via RELAX NG
> Date: 30 Oct 2002 15:51:21 +1100
>
> Many thanks to the excellent work from Colin Adams
> to prepare the draft sitemap RNG grammar.
> 
> There is now a "validate" target in the main build.xml
> of head 2.1 CVS only. Call it explicitly with
> ./build.sh validate ... no other targets depend on it yet.
> 
> Please try it out. Build-time validation is being done
> for **/sitemap.xmap and **/cocoon.roles
> 
> The sitemaps and/or the draft RNG grammar now need
> tweaking and we need RNG grammars for other config files.
> 
> If people are happy with this infrastructure, then we can
> subsequently vote whether to enable it implicitly during
> the build.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to