W3C home > Mailing lists > Public > www-validator-css@w3.org > July 2011

CSS Validator doesn't build with ant out of the box... build.xml needs updating.

From: Robert Pocklington <rpocklin@gmail.com>
Date: Wed, 6 Jul 2011 21:31:48 +1000
Message-ID: <CAFwMonVy=q4HqycpfMzV4uD2QGk4sasm0SHrYRC5My5K_Lhp5Q@mail.gmail.com>
To: www-validator-css@w3.org
Hi,

Two things, first is I found the CSS Validator build.xml needs updating,
there is a diff patch here:
http://www.w3.org/Bugs/Public/attachment.cgi?id=1007&action=edit
but this should be checked in to the mainline.  It seems to fail because the
dependencies have been deleted from the Apache website, and the fact it
needs
a servlet.jar in the classpath.

Second is that there is very little documentation on the web about running
the CSS Validator locally - even once you compile it and create a valid jar,
I found it easiest to hunt through the source code to determine the command
line options (including the hidden *-output json* option).

Also the return code appears to be 0 even if there are CSS errors, for most
build infrastructure, a 1 would be better (eg. System.exit(1)).

Would the W3C consider moving this to a github project (being open source)
this way people could contribute pull requests to add approved features
and maintain this validator to keep it current (especially with the new CSS3
features).

All in all, this is a great tool which is currently the canonical source for
'valid' CSS on the web.
Many thanks to the contributors.

Kind Regards,
Robert Pocklington
Received on Friday, 8 July 2011 07:17:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:14:27 GMT