[
http://jira.codehaus.org/browse/MOJO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92604
]
Jerome Lacoste commented on MOJO-735:
-------------------------------------
Jochen,
if I get Mark correctly, he means e.g. using a multimodule project,
pom.xml
xslt-files/pom.xml
xslt-files/src/main/resources/myfile.xslt <-- gets packaged in jar
project/pom.xml <-- contains both a dependency on xslt-files project and
uses myfile.xslt as resource.
You probably have to support both file and resource loading: If configLocation
is a URI, take it from the specified location otherwise (1) try to load it as
a relative location from current basedir and if that fails (2) try to load it
as a resource.
(1) and (2) can be inverted, but maybe use the same order as done by the
checkstyle plugin.
Note: you could take this for beta-3, and release beta-2 :)
> Allow XSL to be obtained from classloader resources
> ---------------------------------------------------
>
> Key: MOJO-735
> URL: http://jira.codehaus.org/browse/MOJO-735
> Project: Mojo
> Issue Type: Improvement
> Components: xml
> Reporter: Mark Hobson
> Assignee: Jochen Wiedmann
>
> It'd be handy to be able to use classloader resources when specifying the
> XSL. This would work in the same way as the maven-checkstyle-plugin's
> configLocation param, which I believe utilises the plexus ResourceManager.
> This would allow XSLs to be brought in from external resource jars by
> specifying an appropriate plugin dependency.
--
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
