ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53405] New: ExtensionPoint doesn't work with nested import/include
Date Tue, 12 Jun 2012 20:59:49 GMT

          Priority: P2
            Bug ID: 53405
           Summary: ExtensionPoint doesn't work with nested import/include
          Severity: normal
    Classification: Unclassified
                OS: Linux
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Core
           Product: Ant

Created attachment 28923
enhanced extension-point-test.xml to reproduce the use case with nested

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

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.

View raw message