You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/02/06 11:18:55 UTC

[maven-bug] Closed: (MAVEN-116) Imported jelly script cannot reference a filterset with refid inside copy task

Message:

   The following issue has been closed.

   Resolver: Peter Lynch
       Date: Thu, 6 Feb 2003 4:18 AM

Jelly has been patched and this should no longer be a problem. I have verified with code I have in the webserver plugin.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-116
    Summary: Imported jelly script cannot reference a filterset with refid inside copy task
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: jelly-integ
    Fix For: 1.0-beta-8
   Versions:
             1.0-beta-7

   Assignee: james strachan
   Reporter: Peter Lynch

    Created: Thu, 26 Sep 2002 6:47 PM
    Updated: Thu, 6 Feb 2003 4:18 AM
Environment: Win 2000, JDK 1.4

Description:
1. Create a plugin jelly script with a filterset defined inside it.
We'll call it "dummyplugin:init".
2. Import another jelly script with the j:import core tag outside any goal.
 The imported jelly script should have a goal that has a copy task with a nested filterset that uses the refid attribute to refer to the previously defined filterset.

The copy is performed and debuging shows the filtersets get defined, however, the filter tokens are not used in the copy of the files in the copy task.

The import tag has it's inherit property to 'true' and it still does not work.

Yes I need to provide a sample script or test case but hopefully you get the idea :).




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