[
https://issues.apache.org/jira/browse/HADOOP-18223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Norris updated HADOOP-18223:
---------------------------------
Issue Type: Task (was: Bug)
> Publishing maven package in com.hadoop namespace
> ------------------------------------------------
>
> Key: HADOOP-18223
> URL: https://issues.apache.org/jira/browse/HADOOP-18223
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Will Norris
> Priority: Minor
>
> *I'm looking to get opinions on Twitter publishing the hadoop-lzo project on
> maven central in the com.hadoop namespace.*
> Hey, I work in the open source office at Twitter, and we publish the
> [hadoop-lzo project|https://github.com/twitter/hadoop-lzo], which is used by
> a handful of folks. Some of you may know the history better than I, but this
> was an old project from Google Code that got migrated to Twitter's GitHub org
> years ago, and is currently published on our maven host at maven.twttr.com
> (and only there).
> I don't know the full history of why it is only published there, but we've
> had a few incidents of that service being unavailable, [breaking builds for
> downstream users|https://github.com/twitter/hadoop-lzo/issues/148]. I'd like
> to remove this reliance on the maven.twttr.com host by publishing this on
> maven central.
> Ideally, I'd like to do it in a way that requires the least amount of work
> for downstream users, which would mean using the existing group and project
> ID: com.hadoop.gplcompression.hadoop-lzo. The com.hadoop namespace is mostly
> unused on maven ([https://repo1.maven.org/maven2/com/hadoop/])...
> interestingly, only used by what I believe is another fork of the same
> compression library. But since hadoop.com is presumably owned by the Hadoop
> project (whois records are hidden, but it [appears to have always
> redirected|https://web.archive.org/web/*/hadoop.com] to the project website),
> I wanted to run this by someone associated with the project before we did
> this.
> Is there any objection to us publishing this maven library into that
> namespace? The alternative of course is to switch to a com.twitter
> namespace, but that would require more changes for downstream users.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
