You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/07/03 05:38:04 UTC

[jira] [Commented] (AURORA-1213) Consider forking twitter commons java code

    [ https://issues.apache.org/jira/browse/AURORA-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612800#comment-14612800 ] 

Bill Farner commented on AURORA-1213:
-------------------------------------

As [~jfarrell] pointed out on the e-mail list, we will need to seek clearance from Twitter.  I don't foresee this being a big issue.

For context, see http://incubator.apache.org/ip-clearance/index.html

[~caniszczyk], any chance you know who we should reach out to about this?

> Consider forking twitter commons java code
> ------------------------------------------
>
>                 Key: AURORA-1213
>                 URL: https://issues.apache.org/jira/browse/AURORA-1213
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Bill Farner
>            Priority: Minor
>
> We currently have 32  dependencies on libraries from Twitter commons.  
> {noformat}
> $ grep com.twitter.common build.gradle  | wc -l
>       32
> {noformat}
> While these libraries have generally served us well, this number of dependencies creates a transitive web that inhibits us from upgrading our direct dependencies.
> Consider removing these dependencies and replacing our uses of them with forks of the code in our repository.  My hunch is that we use relatively insignificant portions of them overall.  However, if we end up just cloning the sources and maintaining them ourselves, we should back out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)