Version 3.1 was released March 31. Would love an ebuild for it, and regret my own uselessness in this regard. Thanks! Reproducible: Always
Created attachment 280967 [details] lucene-3.3.0.ebuild ebuild for lucene 3.3 that works for me. Known issues: 1. does not build docs behind a proxy due to ant -autoproxy issues 2. does not do tests, at least for me 3. does not install lucli wrapper 4. unable to use junit from distro Major changes: 1. New use flag "contrib" builds all of contrib tree. Removes the need for dev-java/lucene-* builds that were not getting updated. As a consequence, cannot build contrib packages independently. 2. demo package no longer part of core, but part of contrib. 3. ant javacc no longer gets run; didn't work for me
Created attachment 280969 [details] metadata.xml metadata for the new contrib use flag
You say it doesn't build docs from behind a proxy. Does it build when there is no internet connectivity? That's a show-stopper IMHO.
(In reply to comment #3) > You say it doesn't build docs from behind a proxy. Does it build when there is > no internet connectivity? That's a show-stopper IMHO. It builds, but it does not build docs. That is, it fails with "docs" useflag. There are many ant-based java builds that exhibit this behavior. Ant typically downloads javadocs templates from java.org at run time. It would be nice if the java team would make it so at least autoproxy worked and was enabled by default. I would guess that a majority of users are behind firewalls at this point, and a lot of java runtimes (not just ant builds) have this issue. Simply enabling autoproxy in ant did not work for me. I suspect that gnuconfig (20110202) may properly support autoproxy.
(In reply to comment #4) > (In reply to comment #3) > > You say it doesn't build docs from behind a proxy. Does it build when there is > > no internet connectivity? That's a show-stopper IMHO. > > It builds, but it does not build docs. That is, it fails with "docs" useflag. > There are many ant-based java builds that exhibit this behavior. Ant typically > downloads javadocs templates from java.org at run time. > > It would be nice if the java team would make it so at least autoproxy worked > and was enabled by default. I would guess that a majority of users are behind > firewalls at this point, and a lot of java runtimes (not just ant builds) have > this issue. Simply enabling autoproxy in ant did not work for me. I suspect > that gnuconfig (20110202) may properly support autoproxy. I meant may *not* properly support autoproxy
Update per your list. 1. (docs build), solved. 2. tests w/ bundled junit-4.7 work 3. I don't see lucli anywhere in the distfile 4. tests w/ system junit-4.8 fail :-(
You mention lucene-* packages. I don't see them in the tree at all, what were you talking about?
Since I'm at ApacheCon, I cornered somebody about this... (In reply to comment #6)> 2. tests w/ bundled junit-4.7 work > Update per your list. > 1. (docs build), solved. And even better. > 3. I don't see lucli anywhere in the distfile Upstream has deprecated it. > 2. tests w/ bundled junit-4.7 work > 4. tests w/ system junit-4.8 fail :-( Now upstream has delegated it to me to fix the testrunner for this...
upstream also notes that 3.3 should NOT be used, so we're going to jump straight to 3.4.
*** This bug has been marked as a duplicate of bug 392953 ***
