[
https://issues.apache.org/jira/browse/RANGER-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zsombor Gegesy updated RANGER-1731:
-----------------------------------
Attachment: 0001-RANGER-1731-Exclude-old-guava-versions-which-could-c.patch
> Guava dependency cause build problems
> -------------------------------------
>
> Key: RANGER-1731
> URL: https://issues.apache.org/jira/browse/RANGER-1731
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 1.0.0
> Reporter: Zsombor Gegesy
> Assignee: Zsombor Gegesy
> Labels: build-failure
> Attachments:
> 0001-RANGER-1731-Exclude-old-guava-versions-which-could-c.patch
>
>
> In some build environments, maven fails with :
> {code}
> 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]
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
