https://issues.apache.org/bugzilla/show_bug.cgi?id=53405
Priority: P2
Bug ID: 53405
Assignee: [email protected]
Summary: ExtensionPoint doesn't work with nested import/include
Severity: normal
Classification: Unclassified
OS: Linux
Reporter: [email protected]
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.
