[ 
https://issues.apache.org/jira/browse/SLING-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reassigned SLING-361:
--------------------------------------

    Assignee: Carsten Ziegeler

> The sling/sample module fails to compile JSP scripts when run in a reactor 
> build
> --------------------------------------------------------------------------------
>
>                 Key: SLING-361
>                 URL: https://issues.apache.org/jira/browse/SLING-361
>             Project: Sling
>          Issue Type: Bug
>          Components: JSP
>    Affects Versions: 2.0.0
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: 2.0.0
>
>
> JSP script file compilation with the maven-jspc-plugin fails when run in 
> reactor mode build. The problem seems to be that the tag library cannot be 
> resolved:
> [INFO] [jspc:jspc {execution: compile-jsp}]
> [ERROR] Compilation Failure
> org.apache.sling.scripting.jsp.jasper.JasperException: The absolute uri: 
> http://sling.apache.org/taglibs/sling/1.0 cannot be resolved in either 
> web.xml or the jar files deployed with this application
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:315)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:148)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseTaglibDirective(Parser.java:420)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseDirective(Parser.java:476)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseElements(Parser.java:1426)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Parser.parse(Parser.java:133)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.ParserController.doParse(ParserController.java:216)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.ParserController.parse(ParserController.java:103)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Compiler.generateJava(Compiler.java:168)
>         at 
> org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:307)
>         at org.apache.sling.maven.jspc.JspcMojo.processFile(JspcMojo.java:360)
>         at 
> org.apache.sling.maven.jspc.JspcMojo.executeInternal(JspcMojo.java:313)
>         at org.apache.sling.maven.jspc.JspcMojo.execute(JspcMojo.java:225)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>  
> The interesting question - once again - is why the build succeeds in single 
> build but not in a reactor build. Probably there is some project resolution 
> issue. Will have to trace this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to