Re: [bcel] broken repo?

2019-05-06 Thread Gary Gregory
Thank you Sebb! Watching the tix... Gary On Mon, May 6, 2019 at 3:36 PM sebb wrote: > https://issues.apache.org/jira/browse/INFRA-18339 > > On Mon, 6 May 2019 at 19:24, Rob Tompkins wrote: > > > > > > > > > On May 6, 2019, at 2:14 PM, sebb wrote: > > > > > > Same issue applies to commons-net

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Virendra singh Rajpurohit
Thanks Rob,I'll be in touch with you. [image: photo] *Virendra Singh Rajpurohit* +91 9760781615 | virendrasing...@gmail.com Skype: virendrasinghrp <#> Create your own email signature

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Udit Arora
Thanks for offering me an invitation. I would like the invitation. On Tue, 7 May 2019, 12:14 am Eric Barnhill, wrote: > Udit you are welcome to join us to chat on the channel. Do you want an > invitation? > > On Mon, May 6, 2019 at 11:13 AM Udit Arora wrote: > > > Congrats Ben. > > > > On Mon,

Re: [bcel] broken repo?

2019-05-06 Thread sebb
https://issues.apache.org/jira/browse/INFRA-18339 On Mon, 6 May 2019 at 19:24, Rob Tompkins wrote: > > > > > On May 6, 2019, at 2:14 PM, sebb wrote: > > > > Same issue applies to commons-net and -daemon. > > However commons-io and -lang are OK. > > > > Looks like the default branch has not been

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Rob Tompkins
Virendra, Congrats. I’ve signed up to help mentor here. So it’ll be Eric as well as myself helping. All the best, -Rob > On May 6, 2019, at 2:56 PM, Virendra singh Rajpurohit > wrote: > > Yes, it is my preferred mail. > > > > [image: Mailtrack] >

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Virendra singh Rajpurohit
Yes, it is my preferred mail. [image: Mailtrack] Sender notified by Mailtrack 05/07/19, 12:25:37 AM [ima

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Eric Barnhill
On Mon, May 6, 2019 at 11:51 AM Virendra singh Rajpurohit < virendrasing...@gmail.com> wrote: > Hey Eric, My name is there on projects list, but I haven't yet received any > official mail from Apache or Google. > Does that mean I'm selected? > Yes, congratulations you were selected. Check the sp

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Virendra singh Rajpurohit
Hey Eric, My name is there on projects list, but I haven't yet received any official mail from Apache or Google. Does that mean I'm selected? Also I would like to know more about communication channel that we will be using. -- Warm Regards [image: photo] *Virendra Singh Rajpurohit* +91 9760781615

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Eric Barnhill
Udit you are welcome to join us to chat on the channel. Do you want an invitation? On Mon, May 6, 2019 at 11:13 AM Udit Arora wrote: > Congrats Ben. > > On Mon, 6 May 2019, 11:42 pm Ben Nguyen, wrote: > > > Hello, > > > > Any update on which communication tool will be used? Slack, Zulip? I’m >

Re: [bcel] broken repo?

2019-05-06 Thread Rob Tompkins
> On May 6, 2019, at 2:14 PM, sebb wrote: > > Same issue applies to commons-net and -daemon. > However commons-io and -lang are OK. > > Looks like the default branch has not been set up correctly for some > of the repos (probably the ones that were migrated last). > > How does one set the def

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Eric Barnhill
I didn't realize that and perhaps I should have wrapped up that discussion more clearly. Apologies. I thought Mark's suggestion was very good. All would take place at the official Apache slack channel. I set up a commons-gsoc channel and invited Ben and Abhishek. Certainly, that solves all the iss

Re: [bcel] broken repo?

2019-05-06 Thread sebb
Same issue applies to commons-net and -daemon. However commons-io and -lang are OK. Looks like the default branch has not been set up correctly for some of the repos (probably the ones that were migrated last). How does one set the default branch? On Mon, 6 May 2019 at 19:09, Rob Tompkins wrote

Re: [numbers][rng[GSoC] Slack for GSoC mentees

2019-05-06 Thread Abhishek Dhadwal
+1 I'd like to know if the zulip chat would be available for RNG members also ! Look forward to working alongside all the members of the organization. Regards, Abhishek On Mon, May 6, 2019, 23:42 Ben Nguyen wrote: > Hello, > > Any update on which communication tool will be used? Slack, Zulip? I

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Eric Barnhill
Sounds like the word is out. Ben is this your preferred email for a slack communication? I will invite you to our dedicated ASF commons-gsoc slack channel. On Mon, May 6, 2019 at 11:12 AM Ben Nguyen wrote: > Hello, > > Any update on which communication tool will be used? Slack, Zulip? I’m > exci

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Rob Tompkins
> On May 6, 2019, at 2:13 PM, Udit Arora wrote: > > Congrats Ben. +1 Congrats, Ben. I think we’re trying to sort out what messaging system we’re going to use. -Rob > > On Mon, 6 May 2019, 11:42 pm Ben Nguyen, wrote: > >> Hello, >> >> Any update on which communication tool will be use

RE: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Ben Nguyen
Thank you Udit, looking forward to working with you. And yes, this will be my preferred email for all gsoc related communication. From: Udit Arora Sent: Monday, May 6, 2019 1:13 PM To: Commons Developers List Subject: Re: [numbers][GSoC] Slack for GSoC mentees Congrats Ben. On Mon, 6 May 2019

RE: [numbers][rng[GSoC] Slack for GSoC mentees

2019-05-06 Thread Abhishek Dhadwal
Yes sir. Sent from Mail for Windows 10 From: Eric Barnhill Sent: 06 May 2019 23:46 To: Commons Developers List Subject: Re: [numbers][rng[GSoC] Slack for GSoC mentees Hi Abishek, is this your preferred email? On Mon, May 6, 2019 at 11:14 AM Abhishek Dhadwal wrote: > +1 > I'd like to know if t

Re: [numbers][rng[GSoC] Slack for GSoC mentees

2019-05-06 Thread Eric Barnhill
Hi Abishek, is this your preferred email? On Mon, May 6, 2019 at 11:14 AM Abhishek Dhadwal wrote: > +1 > I'd like to know if the zulip chat would be available for RNG members also > ! > Look forward to working alongside all the members of the organization. > Regards, > Abhishek > > > On Mon, May

Re: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Udit Arora
Congrats Ben. On Mon, 6 May 2019, 11:42 pm Ben Nguyen, wrote: > Hello, > > Any update on which communication tool will be used? Slack, Zulip? I’m > excited to get started! > > Ben > > From: Mark Thomas > Sent: Wednesday, May 1, 2019 4:21 PM > To: Commons Developers List > Subject: Re: [numbers][

RE: [numbers][GSoC] Slack for GSoC mentees

2019-05-06 Thread Ben Nguyen
Hello, Any update on which communication tool will be used? Slack, Zulip? I’m excited to get started! Ben From: Mark Thomas Sent: Wednesday, May 1, 2019 4:21 PM To: Commons Developers List Subject: Re: [numbers][GSoC] Slack for GSoC mentees On 01/05/2019 22:09, Eric Barnhill wrote: > Thanks Ma

Re: [bcel] broken repo?

2019-05-06 Thread Rob Tompkins
looking now. -Rob > On May 6, 2019, at 1:23 PM, Gary Gregory wrote: > > Hi All: > > When I try a clean checkout of BCEL I get: > > C:\git>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git > Cloning into 'commons-bcel'... > remote: Counting objects: 21585, done. > remote: Compressi

Re: [bcel] broken repo?

2019-05-06 Thread Rob Tompkins
I wonder if the default branch, “trunk,” no longer exists and that’s what it’s trying to clone down onto. When I run the following it works: git clone --single-branch --branch master https://gitbox.apache.org/repos/asf/commons-bcel.git -Ro

[bcel] broken repo?

2019-05-06 Thread Gary Gregory
Hi All: When I try a clean checkout of BCEL I get: C:\git>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git Cloning into 'commons-bcel'... remote: Counting objects: 21585, done. remote: Compressing objects: 100% (2646/2646), done. Receiving objects: 100% (21585/21585), 3.83 MiB | 4.3

Re: [ANNOUNCEMENT] Apache Commons BCEL 6.3.1

2019-05-06 Thread Gary Gregory
Hi Mark, I can't recall the details ATM and I don't want to take the time to look at logs, but what matters IMO is that: - The build is passing: https://travis-ci.org/apache/commons-bcel (incidentally, the Travis build uses -Ddoclint:none) - You get appropriate warnings on the command line when y

RE: [ANNOUNCEMENT] Apache Commons BCEL 6.3.1

2019-05-06 Thread Mark Roberts
I'm very confused by a change made to pom.xml that removed the Javadoc additionalparm of -Xdoclint:none but nothing was done to the bcel source files to fix all the Javadoc warnings. Help me understand why this was done. Thank you, Mark Roberts > -Original Message- > From: Gary