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

Dont fail if class mentioned in signatures dont exist #31

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Closed

Dont fail if class mentioned in signatures dont exist #31

GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Labels
auto-migrated bug

Comments

@GoogleCodeExporter
Copy link 

Hey there,

this can be completely closed as invalid. I just stumbled over a problem, when 
starting a new project that used an existing signatures file. This file 
included signatures from classes that were not referenced as dependency in the 
new project. Therefore the build failed (using mvn).

Bug or feature? You decide :-)

Maybe printing a warning message is sufficient then?

Original issue reported on code.google.com by [email protected] on 8 Aug 2014 at 10:56
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 bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter