----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63987/#review191693 -----------------------------------------------------------
With the latest code, I can not reproduce this issue. The previous version had this problem when you set policymgr_http_enabled equal to false in install.properties file before installed the security admin. Please refer to RANGER-1858. Please confirm whether they are the same kind of problem. And further confirm the existence of this problem using the lastest code. - pengjianhua On 十一月 21, 2017, 4:01 p.m., Zsombor Gegesy wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/63987/ > ----------------------------------------------------------- > > (Updated 十一月 21, 2017, 4:01 p.m.) > > > Review request for ranger. > > > Bugs: RANGER-1905 > https://issues.apache.org/jira/browse/RANGER-1905 > > > Repository: ranger > > > Description > ------- > > As ranger-plugins-audit doesn't exclude guava from hadoop common, an older > guava > is leaked into embeddedwebserver classpath, which somehow filtered out by the > assembly plugin. > If we explicitly exclude the old guava, and include the new (17.0) guava in > ranger-plugins-audit module, the generated tar.gz/zip distributions will > contain the necessary guava-17.0.jar in ews/lib path. > > > Diffs > ----- > > agents-audit/pom.xml c8bd1d8f3 > > > Diff: https://reviews.apache.org/r/63987/diff/1/ > > > Testing > ------- > > Tested with executing: > > mvn -DskipTests package assembly:assembly; > unzip -Z1 target/ranger-1.0.0-SNAPSHOT-admin.zip | sort > FILES.txt > > And comparing the results with different versions. With the patch, the guava > jar appears correctly. > > > Thanks, > > Zsombor Gegesy > >
