[
http://jira.codehaus.org/browse/MJSPC-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87016
]
fabrizio giustina commented on MJSPC-4:
---------------------------------------
the problem is simply that according to jsp specs tlds are loaded automatically
only from jars in the classpath, and not from class folders (unexpanded tlds
are only read in WEB-INF/lib or subdirectories).
When a project available in a multiproject build is used by another project in
the same build maven directly references the project path instead of the
installed jar.
This could probably be fixed using a manual dependency resolution (this is done
for example in the eclipse plugin) or maybe from the jspc side by making tld
files "virtually" deployed into WEB-INF/lib (I did this some time ago in order
to make taglibrary projects directly usable in eclipse without deploying them.
Such custom DirContext implementation is now available directly in tomcat 6
http://issues.apache.org/bugzilla/show_bug.cgi?id=41260 but I am not sure there
is a way to use this when directly calling jspc).
> JSPs Cannot Be Compiled if They Depend on Tag Files
> ---------------------------------------------------
>
> Key: MJSPC-4
> URL: http://jira.codehaus.org/browse/MJSPC-4
> Project: Maven 2.x Jspc Plugin
> Issue Type: Bug
> Reporter: Stephen Duncan Jr
> Attachments: jspc-example-revised.zip, jspcexample.zip
>
>
> At a minimum, if a tag library is provided as a jar, and the tags are
> implemented as tag files, then the JSP compilation fails. The tag files need
> to be compiled first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
