I opened https://issues.apache.org/jira/browse/LUCENE-4763 about this! Patch is 
under preparation...

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -----Original Message-----
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Thursday, February 07, 2013 11:16 PM
> To: dev@lucene.apache.org
> Subject: Re: documentation-lint and IBM J9
> 
> Thats a nice idea: fail by default (for developers) but have a -D for jenkins.
> 
> On Thu, Feb 7, 2013 at 5:12 PM, Shai Erera <ser...@gmail.com> wrote:
> > I understand. Is it possible to override the failure somehow, so that
> > Jenkins won't fail, but we do?
> >
> > It happened to me again (this time, missing package.html), even though
> > I ran w/ Oracle 1.6, until Robert told me that's broken too! :)
> >
> > Shai
> >
> >
> > On Fri, Feb 8, 2013 at 12:06 AM, Uwe Schindler <u...@thetaphi.de> wrote:
> >>
> >> Because when it fails the build, we cannot run the Jenkins builds
> >> with IBM J9. The JDK is randomly configured/choosen and IBM J9 was (is)
> also used.
> >> But I disabled it a few weeks ago, because of the crashes and
> >> miscompiled code. I think this is fixed now – Mike? If I reenable the
> >> IBM J9 1.6 and 1.7 on Policeman Jenkins (which I really should do),
> >> then it would fail the build, because IBM’s Javadocs are formatted in
> >> a way that the Python linter does not understand (as far as I
> >> remember they were not broken, but *different*).
> >>
> >>
> >>
> >> Uwe
> >>
> >>
> >>
> >> -----
> >>
> >> Uwe Schindler
> >>
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >>
> >> http://www.thetaphi.de
> >>
> >> eMail: u...@thetaphi.de
> >>
> >>
> >>
> >> From: Shai Erera [mailto:ser...@gmail.com]
> >> Sent: Thursday, February 07, 2013 10:41 PM
> >> To: dev@lucene.apache.org
> >> Subject: Re: documentation-lint and IBM J9
> >>
> >>
> >>
> >> 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 <u...@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: u...@thetaphi.de
> >>
> >>
> >>
> >> From: Shai Erera [mailto:ser...@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
> >>
> >>
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional
> commands, e-mail: dev-h...@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to