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] ExtensionPoint doesn't work with nested import/include
Date: Tue, 12 Jun 2012 21:08:48 +0000
Message-ID: <bug-53405-48744-bHcglmqWyL@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-53405-48744@https.issues.apache.org/bugzilla/>
References: <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

Jean-Louis Boudart <jlboudart@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #28923|0                           |1
        is obsolete|                            |

--- Comment #1 from Jean-Louis Boudart <jlboudart@apache.org> ---
Created attachment 28924
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=28924&action=edit
patch to add support of extensionpoint with nested import and include

The problems seems to come when ProjectHelper duplicate the extension point
while importing a build file.
ProjectHelper2 implementation is cloning the extension point as if it was a
Target (using Target clone constructor).
Then, implementation check instanceof extension point and fails with the
message mentioned in original description as it is a Target instance and not an
ExtensionPoint instance.

I attached a patch to fix this.

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