maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (MAVEN-228) Importing a jelly script used to expose goals definied in it.
Date Mon, 04 Aug 2003 04:46:36 GMT
The following issue has been updated:

    Updater: dion gillard (
       Date: Sun, 3 Aug 2003 11:45 PM
             timeoriginalestimate changed from 0
             timeestimate changed from 0 minutes
             Fix Version changed to 1.0-final
For a full history of the issue, see:

View the issue:

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: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:

   Reporter: David Eric Pugh

    Created: Wed, 29 Jan 2003 5:43 PM
    Updated: Sun, 3 Aug 2003 11:45 PM
Environment: W2k with CVS Head

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

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"/>

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

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

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message