[lang] Todo utility class

I have often thought about creating a utility class that allows me to write skeletal code that still compiles but will remind me to go back and finish it. This is a weird meta area of programming, but here are some basic usage examples: Foo foo = Todo.todo(); //returns null Bar bar =

[GitHub] commons-text issue #77: Annotated version

Github user coveralls commented on the issue: https://github.com/apache/commons-text/pull/77 [](https://coveralls.io/builds/15979804) Coverage remained the same at 97.74% when pulling

[GitHub] commons-text pull request #77: Annotated version

Github user NhatDinh closed the pull request at: https://github.com/apache/commons-text/pull/77 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text pull request #77: Annotated version

GitHub user NhatDinh opened a pull request: https://github.com/apache/commons-text/pull/77 Annotated version You can merge this pull request into a Git repository by running: $ git pull https://github.com/NhatDinh/commons-text annotated-version Alternatively you can review

[CANCEL][VOTE] Release Commons JCS 2.2.1 based on RC3

Think I didn't send the cancel mail - gmail didn't find it at least, if I did please ignore. Since the thread is very old and was not straight forward it would be very weird to keep it now so it is probably cleaner to start fresh with a RC4 or even a 2.3 a bit later. Sorry for the delay. Romain

Re: Github usage

When you have a GitHub origin, you can checkout pulls/42/head to check out PR#42. You can pull/merge from that branch as well to merge the PR (by committing and pushing that merge, GitHub will notice and mark the PR as merged). You can also use the "hub" command line tool that GitHub publishes

Re: Github usage

Hi. On Wed, 14 Mar 2018 14:16:42 +, Otto Fowler wrote: I should be more specific, this is for looking at github pr’s. So if your submitters are forking, submitting prs on github. We also have scripts for committing, but we are doing git -> github mirror My knowledge of "git" is small;

Re: Jenkins build is back to normal : commons-validator #64

On Wed, Mar 14, 2018 at 8:46 AM, sebb wrote: > FIxed by changing the Jenkins JDK to 1.8 (latest). > > Also had to exclude some nodes (e.g. cassandra-*) which don't seem to > have publish rights. > Ugh, what a mess :-( Gary > > On 14 March 2018 at 13:42, Apache Jenkins

Re: Jenkins build is back to normal : commons-validator #64

FIxed by changing the Jenkins JDK to 1.8 (latest). Also had to exclude some nodes (e.g. cassandra-*) which don't seem to have publish rights. On 14 March 2018 at 13:42, Apache Jenkins Server wrote: > See

Re: Github usage Was: [Statistics] Port codes from Commons Math

I should be more specific, this is for looking at github pr’s. So if your submitters are forking, submitting prs on github. We also have scripts for committing, but we are doing git -> github mirror On March 14, 2018 at 10:15:04, Otto Fowler (ottobackwa...@gmail.com) wrote: We have script to

Re: Github usage Was: [Statistics] Port codes from Commons Math

We have script to help reviewers checkout PR’s in git, either in their own repo or just doing it in ~/tmp or something into a new repo. So, I would run: > checkout-pr 999 in the tmp directory, and end up with a local version that I can then build and do whatever with. would that help? On

Re: Github usage Was: [Statistics] Port codes from Commons Math

On Tue, 13 Mar 2018 11:43:17 -0400, ajs6f wrote: On Mar 13, 2018, at 11:20 AM, Gilles wrote: I didn't find it very easy to cooperate with developers who fork on GitHub and submit PRs. I've now found the "git" command that creates a branch from a PR, but it

Re: [Statistics] Port codes from Commons Math

Hi. On Tue, 13 Mar 2018 23:37:24 +0530, Gimhana Nadeeshan wrote: Hello Devs, Thanks Gilles and Eric for guidance. I have cloned the Commons repos and forked the Common's Stat repo. Is it possible to make pull requests to that repo to be reviewed? That's certainly possible, but I'm afraid

Re: [VALIDATOR] Update of packages used by Validator?

On Tue, 13 Mar 2018 15:51:39 -0400, Rob Tompkins wrote: On Mar 13, 2018, at 3:48 PM, Gary Gregory wrote: On Tue, Mar 13, 2018 at 1:47 PM, Rob Tompkins wrote: [...] My plan is to test run commons-parent 45 on the next release. I’m indifferent

AW: Build failed in Jenkins: commons-validator #61

It seems that there is lot of work on the nodes ATM. So we have to wait for results ... Jan > -Ursprüngliche Nachricht- > Von: Jan Matèrne (jhm) [mailto:apa...@materne.de] > Gesendet: Mittwoch, 14. März 2018 09:33 > An: 'Commons Developers List' > Betreff: AW: Build failed in Jenkins:

AW: Build failed in Jenkins: commons-validator #61

I solved the same problem for commons-email. https://builds.apache.org/view/All/job/commons-email/configure The project requires via the chosen Maven profile a specific Java version. This Java installation must be available via a specific environment variable "JAVA_1_7_HOME". commons-validator