On Mon, Mar 29, 2010 at 3:11 PM, Justin Edelson <[email protected]> wrote: > These aren't fatal errors by any stretch of the imagination. The JSP errors > arise from the fact that Sling's JSP support doesn't follow JavaEE standards > with respect to TLDs. The web.xml error is trivial to fix (and has been > fixed in r928763) although it caused no runtime problems as this file is > ignored by Sling. > > Justin > Going a little further, i replaced my settings.xml, which used an enterprise proxy (as sliung seems to use maven-assembly-plugin 2.2 beta 5) and was able to let sling build. unfortunatly, the build ends due to test errors :
Tests run: 312, Failures: 312, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. I perfectly know I could disable test, but I find rather disturbing to have all tests failing. As a consequence, like Bertrand told me, I will use a tagged build version, for which tests ran successfully. -- Nicolas Delsaux
