lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shai Erera <ser...@gmail.com>
Subject Re: documentation-lint and IBM J9
Date Thu, 07 Feb 2013 21:40:57 GMT
I see, but is it possible to FAIL the build in that case? I ran with
Oracle's 1.6.0 and it was ok

Shai


On Thu, Feb 7, 2013 at 11:39 PM, Uwe Schindler <uwe@thetaphi.de> wrote:

> We ran the llinter with IBM J9 on the Policeman Jenkins server, but the
> generated Javadocs were full of borken links and invalid HTML. So it looks
> like the Javadoc generator of IBM J9 is not compatible with the python
> checker.****
>
> ** **
>
> This is why it is disabled.****
>
> ** **
>
> -----****
>
> Uwe Schindler****
>
> H.-H.-Meier-Allee 63, D-28213 Bremen****
>
> http://www.thetaphi.de****
>
> eMail: uwe@thetaphi.de****
>
> ** **
>
> *From:* Shai Erera [mailto:serera@gmail.com]
> *Sent:* Thursday, February 07, 2013 10:30 PM
> *To:* dev@lucene.apache.org
> *Subject:* documentation-lint and IBM J9****
>
> ** **
>
> Hi****
>
> I ran 'precommit' and noticed in the end a WARN message that
> documentation-lint doesn't work w/ J9 1.6.0.****
>
> While I'm interested to know why (and whether it's just 1.6), can we make
> the build fail in that case? I think that some of my recent Jenkins build
> failures were related to it -- I ran precommit, but just didn't notice the
> WARN message - I only looked at BUILD SUCCESSFUL.****
>
> I don't mind if the build fails as early as precommit starts .. just to
> make sure whoever runs it, works w/ a supported JVM.****
>
> Is it possible?****
>
> Shai****
>

Mime
View raw message