- From: Michael[tm] Smith <mike@w3.org>
- Date: Mon, 13 Oct 2014 23:08:41 +0900
- To: www-validator@w3.org
- Message-ID: <20141013140841.GO1150@jay.w3.org>
This is just a heads-up to anybody building and running the Nu Markup Checker (validator.nu HTML5 validator) from the github sources. We've moved all the sources to https://github.com/validator/validator/ and also changed the build instructions. The new instructions are at: http://validator.github.io/validator/#build-instructions It just amounts to cloning https://github.com/validator/validator.git instead of https://github.com/validator/build.git The old/existing build script has been changed such that after you pull the latest version of it and run it (e.g., when doing "./build.py all"), it'll now just exit with a message saying that the build script has moved to http://validator.github.io/validator/#build-instructions But If you're not ready to update to the new build environment yet, you can still force the old build script to run by specifying the "--legacy" option: python build/build.py --legacy all But note that the code you'd be building and running from in that case is frozen, so you wouldn't ever get any further updates unless/until you move to the new build setup. If you run into any problems with either the old or new build setups, please either report it at https://github.com/validator/validator/issues or just post a message to this list with the details. Also keep in mind that you don't need to build from the sources in order to run your own instance of the checker. You can now instead just use the latest jar (or war) release: https://github.com/validator/validator/releases Instructions how to run an instance of the checker service using one of those release files are here: http://validator.github.io/validator/#standalone http://validator.github.io/validator/#servlet --Mike -- Michael[tm] Smith http://people.w3.org/mike
Received on Monday, 13 October 2014 14:08:46 UTC