aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1213) Consider forking twitter commons java code
Date Mon, 10 Aug 2015 21:48:45 GMT

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

Zameer Manji commented on AURORA-1213:
--------------------------------------

I believe the IP clearance has been received. [~jfarrell]: Do you know how we can move forward
now?

> 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)

Mime
View raw message