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.

Sign up for GitHub

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

Jump to bottom

Add support for signaturesFilelist and signaturesFile elements #36

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

Add support for signaturesFilelist and signaturesFile elements #36

GoogleCodeExporter opened this issue Mar 14, 2015 · 2 comments
Labels
auto-migrated enhancement

Comments

@GoogleCodeExporter
Copy link 

You should be able to enforce specific signatures files, to *enforce* specific 
files. Filesets are too relaxed, because they simply ignore missing files, 
leading to no checks done.

This allows to do the following:

<forbiddenapis>
 <signaturesFile file="sign.txt"/>
 <siganturesFilelist dir="." files="file1.txt, file2.txt"/>
<forbiddenapis>

Original issue reported on code.google.com by uwe.h.schindler on 14 Sep 2014 at 9:31
@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 

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
@uschindler
Fix issue #35: Allow to ignore empty filesets: <forbiddenapis ignoreE…
67a4d60 
…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
Assignees
No one assigned
Labels
auto-migrated enhancement
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter