Ant script configuring ivy fails with name not found

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.0 Beta 3
• Fix Version/s: 7.0.0 Beta 4
• Component/s: Dev Tools, Dev Tools > Plugins SDK
• Labels: None

When I launch ant build-service, I get this error trace:

BUILD FAILED
/Users/aelian/dev/portal7/plugins/webs/screens-web/build.xml:12: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common-osgi-plugin.xml:5: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common-plugin.xml:5: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common.xml:57: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common-ivy.xml:254: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common-ivy.xml:161: The following error occurred while executing this line:
/Users/aelian/dev/portal7/plugins/build-common-ivy.xml:181: Problem: failed to create task or type set-module-properties
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

The ant script is registering some macros and then executing the process-ivy task that calls the macro set-module-properties . But it fails because it is defined later on that file.

The process-ivy task should be called after defining all tasks needed.

Related to LPS-61420