Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't require an Ant target definition for each Maven goal #39

Open
berndv opened this issue Sep 26, 2014 · 0 comments
Open

Don't require an Ant target definition for each Maven goal #39

berndv opened this issue Sep 26, 2014 · 0 comments
Assignees

Comments

@berndv
Copy link
Member

berndv commented Sep 26, 2014

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.

@berndv berndv self-assigned this Sep 26, 2014
@berndv berndv added this to the Later Versions milestone Sep 26, 2014
@berndv berndv modified the milestone: Later Versions Sep 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant