You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For builds with custom ant targets it is currently required to define a corresponding ant target in the <project>/externalBuild/customTargets.xml file for each maven phase. This is inconvenient, error prone and leads to a lot of unnecessary log messages from empty ant calls during the build process.
The idea is to scan the customTargets.xml for targets named like maven phases and only to execute those during the build.
The text was updated successfully, but these errors were encountered:
For builds with custom ant targets it is currently required to define a corresponding ant target in the
<project>/externalBuild/customTargets.xml
file for each maven phase. This is inconvenient, error prone and leads to a lot of unnecessary log messages from empty ant calls during the build process.The idea is to scan the
customTargets.xml
for targets named like maven phases and only to execute those during the build.The text was updated successfully, but these errors were encountered: