[RANGER-1731] Guava dependency cause build problems

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: admin
• Labels: build-failure
• Flags: Patch, Important
• Assignee: Zsombor Gegesy
• Reporter: Zsombor Gegesy
• Created: 11/Aug/17 12:54
• Updated: 26/Sep/18 19:42
• Resolved: 11/Aug/17 18:28

Description

In some build environments, maven fails with :

2017/08/11 13:46:39 INFO : [ERROR] Failed to execute goal on project security-admin-web: Could not resolve dependencies for project org.apache.ranger:security-admin-web:war:1.0.0-SNAPSHOT: Failed to collect dependencies at com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer:jar:r239 -> com.google.guava:guava:jar:[11.0,): No versions available for com.google.guava:guava:jar:[11.0,) within specified range -> [Help 1]

As guava 17 is already included in the security-admin module, this transitive dependency is not needed at all. So it would be better to exclude it from there, so maven doesn't need to manually calculate versions