Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.0-beta-8
-
Fix Version/s: 1.0-rc3
-
Component/s: jelly/ant integration
-
Labels:None
-
Environment:W2k with CVS Head
-
Number of attachments :
Description
Previously, you could import a jelly script and expose the goals. This was crucially import in the cactus plugin for dynamically importing the scripts for various app servers. At this point, this functionality doesn't work. Should I edit the touchstone code to demonstrate this?
Here is what used to work:
<!-- Import all the jelly scripts found in the maven.cactus.conf.dir
directory. They are jelly scripts to start/stop the different
containers. -->
<fileScanner var="scanner">
<fileset dir="$
" includes="*.jelly"/>
</fileScanner>
<j:forEach var="script" items="$
{scanner.iterator()}">
<j:import inherit="true" uri="$
"/>
</j:forEach>
if you do a maven -g you will see all the included file's goals are not available.
Issue Links
- is duplicated by
-
MAVEN-1161
goal mapper does not follow j:import tags
-
I think this same problem afflicts the j2ee plugin.
This line here doesn't seem to actually work.
<j:import inherit="true" uri="./appserver/tomcat-4.x.jelly" />