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

Only print warning if Ant fileset of classes to scan is empty (like Maven) #35

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

If no classes are in the given fileset, the Ant task should simply print a 
warning instead of failing the build.

This allows multi-module builds to succeed that share one forbidden-apis target.

Original issue reported on code.google.com by uwe.h.schindler on 14 Sep 2014 at 7:56

@GoogleCodeExporter
Copy link
Author

Fixed in commit revision 311.

Original comment by uwe.h.schindler on 14 Sep 2014 at 9:41

  • Changed state: Committed

@GoogleCodeExporter
Copy link
Author

With the committed patch, the current behaviour did not change. But with the 
attribute ignoreEmptyFileset="true" you can ignore the empty fileset or other 
resource collections for multi-module builds.

Original comment by uwe.h.schindler on 14 Sep 2014 at 10:07

@GoogleCodeExporter
Copy link
Author

Released with version 1.7

Original comment by uwe.h.schindler on 24 Nov 2014 at 12:49

  • Changed state: Fixed

uschindler added a commit that referenced this issue Mar 14, 2015
…mptyFileset="true"/>.

Fix issue #36: Allow signaturesFileList and signaturesFile nested elements to enforce existence (does not work with Filesets).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant