Where is the XSSAPI defined? (Maven build issues for /libs/foundation components)
1) Where is the XSSAPI defined? I've included the <dependency> below from the depfinder# tool, and I still get the error, (shown below), when I attempt to run "mvn clean install" in the commons or content directory.
| com.adobe.granite.xss | 1.1.0 | com.day.cq.cq-xssprotection (107) | <dependency> <groupId>com.adobe.granite</groupId> <artifactId>com.adobe.granite.xssprotection</artifactId> <version>5.5.24</version> <scope>provided</scope> </dependency> |
Snippet from Maven log:
[ERROR] Compilation Failure org.apache.sling.scripting.jsp.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 3 in the jsp file: /libs/foundation/components/profile/form/formrowtext.jsp xssAPI cannot be resolved 1: <%@page session="false"%><div class="form_row"> 2: <div class="form_leftcol"> 3: <div class="form_leftcollabel"><label for="<%= xssAPI.encodeForHTMLAttr(path) %>"><%= xssAPI.encodeForHTML(title) %></label></div> 4: <div class="form_leftcolmark <%= required ? "form_required" : ""%>"><%= required ? "*" : " " %></div> 5: </div>a 6: <div class="form_rightcol"><%
2) Is there an easier way to determine all of the dependencies needed to build everything off of /libs/foundation/components, without sitting there and working through each and every build error one by one, using the dependency finder tool and adding the <dependency> to the maven POM? There must be a way to do this more efficiently. Also, whenever we migrate to AEM 6.1, I imagine I'll have to update the versions for each dependency one by one, (unless the uber.jar enables maven to build without explicit dependencies being listed in the POM.xml).
