Please be careful. Sorry but hadoop-lzo is GPL licensed. Internally at my employer we don't use/ship hadoop-lzo because of the licensing concerns.
I suppose since the code is GPL we as an Apache project want to stay away from it? On Thu, May 5, 2022 at 11:17 AM Ayush Saxena <ayush...@gmail.com> wrote: > Didn’t read it full. But seems related to some code change in Hadoop Common > Forwarded to common-dev > > Begin forwarded message: > > > From: Will Norris <wnor...@twitter.com.invalid> > > Date: 5 May 2022 at 11:28:35 PM IST > > To: gene...@hadoop.apache.org > > Subject: Publishing hadoop-lzo maven package in com.hadoop namespace > > > > Hey Hadoop folks, > > > > I'm honestly not sure the best place to post this, but general@ seemed > > reasonable enough. I've just opened an issue, HADOOP-18223 > > <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any > > opinions on Twitter publishing our hadoop-lzo package on maven central > > under the current com.hadoop groupId. We've published it this way on > > maven.twttr.com for quite a few years, but are trying to remove that > single > > point of failure <https://github.com/twitter/hadoop-lzo/issues/148> for > > downstream users. > > > > I can't imagine too many people will have strong opinions about this, but > > since it's not our namespace, I wanted to talk with folks before we did > > anything. > > > > -will >
