[
https://issues.apache.org/jira/browse/RANGER-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629306#comment-16629306
]
Abhay Kulkarni commented on RANGER-1731:
----------------------------------------
ranger-0.7:
commit details:
https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=9f4381080524c8ab5a4298726c7e4d82b34c7c40
> 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
> Priority: Major
> Labels: build-failure
> Fix For: 1.0.0
>
> 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
(v7.6.3#76005)
