Re: Ivy+IvyDE: help wanted

Thank you very much Nicolas. Having you around for code reviews and even just watching is definitely going to help a lot. Thanks for merging that patch too. -Jaikiran On 17-May-2017, at 2:09 AM, Nicolas Lalevée wrote: > Le 16 mai 2017 à 13:11, J Pai

Re: Ivy+IvyDE: help wanted

> Le 16 mai 2017 à 13:11, J Pai a écrit : > > Thanks Jan for initiating this. > > On the ICLA front - I already have contributed and continue to contribute to > some other Apache projects (these days mostly via github). Do I still have to > sign the ICLA? Is there

[GitHub] ant-ivy pull request #10: Fix for IVY-1531

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/10 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Ivy+IvyDE: help wanted

Backporting changes from the various forks would be a great idea. On 16 May 2017 at 11:31, Gintautas Grigelionis wrote: > Ivy is also a part of Groovy, through Grapes. There are quite a few forks > of Ivy on GitHub, perhaps it is worth the while to solicit PRs? > >

Re: Ivy+IvyDE: help wanted

Ivy is also a part of Groovy, through Grapes. There are quite a few forks of Ivy on GitHub, perhaps it is worth the while to solicit PRs? Meanwhile, I was asking for help/opinions about https://issues.apache.org/jira/browse/IVY-1478 (updatesite resolver) which would in turn help setting up builds

Re: Ivy+IvyDE: help wanted

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

Re: Ivy+IvyDE: help wanted

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 wrote: On 16-May-2017,

Re: Ivy+IvyDE: help wanted

On 16-May-2017, at 6:09 PM, Jan Matèrne (jhm) 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 >

Re: Ivy+IvyDE: help wanted

On 2017-05-16, Jan Matèrne (jhm) 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

AW: Ivy+IvyDE: help wanted

> On the ICLA front - I already have contributed and continue to > contribute to some other Apache projects (these days mostly via > github). Do I still have to sign the ICLA? The ICLA is for the ASF - so you don't have to sign a new one if you already have submitted one. > Is there a way to

Re: Ivy+IvyDE: help wanted

On 2017-05-16, J Pai wrote: > On the ICLA front - I already have contributed and continue to > contribute to some other Apache projects (these days mostly via > github). Do I still have to sign the ICLA? Whether a CLA is strictly required or not isn't always clear. Strictly speaking the terms

Re: Ivy+IvyDE: help wanted

Thanks Jan for initiating this. On the ICLA front - I already have contributed and continue to contribute to some other Apache projects (these days mostly via github). Do I still have to sign the ICLA? Is there a way to check if I have already signed this ICLA previously? I don’t remember if

[GitHub] ant-ivy pull request #11: IVY-1499 Prevent potential NPE during retrieve

Github user jaikiran closed the pull request at: https://github.com/apache/ant-ivy/pull/11 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ant-ivy issue #11: IVY-1499 Prevent potential NPE during retrieve

Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/11 Closing for now, since I need to revisit this to see if this is still valid --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

Ivy+IvyDE: help wanted

Hello community the Ant PMC hasn't been able to keep up with bugs reported for Ivy and IvyDE for a while now. The number of active committers with the required knowledge of the code base is getting smaller and we are having a hard time evaluating patches. We'd like to revive Ivy and IvyDE, but