@Ranger, Please see the email below which indicates that Ranger WAR file have dependencies that should not be bundled and/or specified in the LICENSE/NOTICE files. Can we review our binary release files to ensure that we are in compliance with Apache Releases?
@Roman: We will try to go through the list and ensure that our LICENSE and NOTICE files are updated with bundled binaries ? (RANGER-1623 <https://issues.apache.org/jira/browse/RANGER-1623>) In the meanwhile, if you can add the details on the files that are not in compliance in the above JIRA, it will greatly help the ranger community to fix it asap. Thanks, Selva- > Begin forwarded message: > > From: Roman Shaposhnik <[email protected]> > Subject: Good examples of licensing in ASF produced web apps? > Date: May 26, 2017 at 5:49:46 PM EDT > To: "[email protected]" <[email protected]> > Reply-To: [email protected] > > Hi! > > I advising a podling on producing a binary release that > includes a Java web app (think war file). I wanted to give > them a taste of what TLPs do so I went to the ones that > I knew were generating war files: Oozie and Ranger. > You know the stuff I'm familiar with in Hadoop ecosystem. > > What he discovered may shock you! No, but seriously. > > Here's what these projects publish on Maven central: > > https://search.maven.org/remotecontent?filepath=org/apache/oozie/oozie-webapp/4.3.0/oozie-webapp-4.3.0.war > https://search.maven.org/remotecontent?filepath=org/apache/ranger/security-admin-web/0.7.0/security-admin-web-0.7.0.war > > Each of these WAR files: > 1. bundles all sorts of dependancies -- not just the bits coming > from the project itself > > 2. Neither provides a meanigful LICENSE nor NOTICE files. > The ones under ./WEB-INF/classes/META-INF are stock ones > and really don't address the binary dependencies bundling > > Have we somehow relaxed the requirements for binary artifacts? > I hope not -- and if not -- what are the good examples of web app > projects doing it right? > > Thanks, > Roman. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
