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
Nicolas Delsaux wrote:
On Mon, Mar 29, 2010 at 11:21 AM, Bertrand Delacretaz
<[email protected]> wrote:
Note that launchpad/testing is the core of the overall integration
testing, if tests fail in there that's bad news.
FYI, When I open the tests projects, I get errors in the following projects :
- org.apache.sling.launchpad.contrib-testing
- org.apache.sling.launchpad.testing
- org.apache.sling.launchpad.test-services
- org.apache.sling.launchpad.test-services-war
The errors typically are
Can not find the tag library descriptor for
"http://sling.apache.org/taglibs/sling/1.0"; b-b.jsp
/org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test/issues/sling457
line
22 JSP Problem (encountered around 20 times)
I guess the file may have been accidentaly (re)moved, and fixing this
error would also fix the following one.
currentNode cannot be
resolved forward-forced.jsp
/org.apache.sling.launchpad.contrib-testing/src/test/resources/integration-test
line
26 JSP Problem (encountered around 20 times)
cvc-attribute.3: The value 'Test Services Webapp' of attribute 'id' on
element 'web-app' is not valid with respect to its type,
'ID'. web.xml
/org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
5 XML Problem
which can easily be fixed by removing all whitespaces characters from
the id element (notice fixing this error also fix the following one)
cvc-datatype-valid.1.2.1: 'Test Services Webapp' is not a valid value
for 'NCName'. web.xml
/org.apache.sling.launchpad.test-services-war/src/main/webapp/WEB-INF line
5 XML Problem
