[maven-bug] New comment: (MAVEN-228) Importing a jelly script used to expose goals definied in it.

[bo...@werken.com]

The following comment has been added to this issue:

     Author: David Eric Pugh
    Created: Wed, 29 Jan 2003 5:50 PM
       Body:
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" />
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-228


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-228
    Summary: Importing a jelly script used to expose goals definied in it.
       Type: Bug

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: jelly-integ
   Versions:
             1.0-beta-8

   Assignee: Jason van Zyl
   Reporter: David Eric Pugh

    Created: Wed, 29 Jan 2003 5:43 PM
    Updated: Wed, 29 Jan 2003 5:43 PM
Environment: W2k with CVS Head

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="${maven.cactus.scripts.dir}" includes="*.jelly"/>
  </fileScanner>

  <j:forEach var="script" items="${scanner.iterator()}">
    <j:import inherit="true" uri="${script.toURL().toString()}"/>
  </j:forEach>


if you do a maven -g you will see all the included file's goals are not available.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira