Re: [Numbers] Jenkins build failure

2018-01-29 Thread Gary Gregory
I think custom tags have to be of the form @com.example.tag. Gary On Jan 29, 2018 02:58, "Gilles" wrote: > On Mon, 29 Jan 2018 10:33:02 +0100, Eric Barnhill wrote: > >> It doesn't like a custom @if tag. >> > > If it is custom, how can the compiler know what it means? > > Is there any reason for

Re: [Numbers] Jenkins build failure

2018-01-29 Thread Gilles
On Mon, 29 Jan 2018 10:33:02 +0100, Eric Barnhill wrote: It doesn't like a custom @if tag. If it is custom, how can the compiler know what it means? Is there any reason for me to keep it? If you don't see a reason, I'm certainly fine replacing "@if" with "if". ;-) It doesn't seem to be us

Re: [Numbers] Jenkins build failure

2018-01-29 Thread Eric Barnhill
It doesn't like a custom @if tag. Is there any reason for me to keep it? It doesn't seem to be used very gramatically anyway. I have started looking through stats as well. On Fri, Jan 26, 2018 at 4:35 PM, Eric Barnhill wrote: > ok will fix > > On Fri, Jan 26, 2018 at 4:23 PM, Gilles > wrote:

Re: [Numbers] Jenkins build failure

2018-01-26 Thread Eric Barnhill
ok will fix On Fri, Jan 26, 2018 at 4:23 PM, Gilles wrote: > Hi Eric. > > Your recent merge contains Javadoc errors that make Java 8 > unhappy: > https://builds.apache.org/view/A-D/view/Commons/job/commons- > numbers/62/console > > Regards, > Gilles > > > --

[Numbers] Jenkins build failure

2018-01-26 Thread Gilles
Hi Eric. Your recent merge contains Javadoc errors that make Java 8 unhappy: https://builds.apache.org/view/A-D/view/Commons/job/commons-numbers/62/console Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.