Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
From: bugzilla@apache.org
To: notifications@ant.apache.org
Subject: [Bug 53405] New: ExtensionPoint doesn't work with nested
 import/include
Date: Tue, 12 Jun 2012 20:59:49 +0000
Message-ID: <bug-53405-48744@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=53405

          Priority: P2
            Bug ID: 53405
          Assignee: notifications@ant.apache.org
           Summary: ExtensionPoint doesn't work with nested import/include
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Reporter: jlboudart@apache.org
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Core
           Product: Ant

Created attachment 28923
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=28923&action=edit
enhanced extension-point-test.xml to reproduce the use case with nested
include/import

ExtensionPoint doesn't work when using nested import/include and fails with a
message "referenced target XXXX is not an extension-point".

Example :
Say we have three distinct build file :
* abstract-compile.xml defining an extension point named "compile"
* compile-java.xml imports abstract-compile.xml and define a concrete target
"compile-java" referenced as an extension-of "compile" 
* build.xml (the main script) including compile-java.xml with a prefix
"myprefix".

When project helper try to handle this use case, the build fail with the
following message :
"referenced target 'compile' is not an extension-point".

-- 
You are receiving this mail because:
You are the assignee for the bug.