The very interesting thing about Ivy, in my opinion, is that while it isn't developed on that much currently, it's still the basis of SBT, Gradle, and probably other build tools that are a bit more popular. I'm curious how all those projects continue to use Ivy while its development seems somewhat stalled here.
On 16 May 2017 at 07:53, J Pai <jai.forums2...@gmail.com> wrote: > Here’s the instructions https://wiki.apache.org/general/PreCommitBuilds > which Kafka team apparently followed. They tracked this activity in this > JIRA https://issues.apache.org/jira/browse/KAFKA-1856 > > -Jaikiran > > On 16-May-2017, at 6:20 PM, J Pai <jai.forums2...@gmail.com> wrote: > > > On 16-May-2017, at 6:09 PM, Jan Matèrne (jhm) <apa...@materne.de> wrote: > > > > > > - From a development point of view, given that there aren’t many who > > are familiar with the codebase, it would really help build some kind of > > confidence level in submitted patches, if the github repo was backed by > > the usual PR processing mechanism that’s associated with many other > > Apache projects out there. What I mean is, submission of each PR > > triggering the builds, testcases through a build automation tool (like > > Jenkins) and reporting back with any issues with existing test cases. > > +1 > I don't know any automatisation of this kind. Someone else? > Something where we could copy that? > > > Apache Kafka are doing this for their github mirror > https://github.com/apache/kafka/pulls. They had a discussion about this > in their mailing list on how to setup. I’ll try and find if there’s some > detailed instructions for Apache projects to follow this model. > > -Jaikiran > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > -- Matt Sicker <boa...@gmail.com>
