Description of problem: The version of lucene in core is 1.4.3; this is very old (November 2004 release date). 2.0.0 has been out since last May, and jpackage.org has packages of 1.9.1 that could possibly be the basis for a new version. I don't actually directly use lucene, but it's a dependency of eclipse which I do use. The newest eclipse depends also on lucene-devel, which *isn't* a separate package at jpackage and which therefore broke my attempted update today. (I know third-party repos aren't supported, but I wanted to explain why I noticed this.) Version-Release number of selected component (if applicable): 1.4.3-1jpp.14
ping? lucene 2.3.0 is now available: http://lucene.apache.org/java/docs/
Will 2.3.0 work with Eclipse 3.3.x?
(In reply to comment #2) > Will 2.3.0 work with Eclipse 3.3.x? Even if it didn't that's definitely no excuse for not updating the package. Compat packages can be made if necessary. (We should definitely look at Eclipse once this is upgraded, and that's best done before we do the release -- hence the F9Target).
Created attachment 295308 [details] Diff between lucene-1.9.1-2jpp.5 and lucene-2.3.0-1jpp This worked for me, though I did not attempt a mock build.
Created attachment 295416 [details] Diff between lucene-1.9.1-2jpp.5 and lucene-2.3.0-1jpp Less invasive changes, so I don't break the build. Should build fine in mock this time.
Please ensure that the new lucene works with Eclipse.
Thanks for the patch Lubomir. Please note the naming convention, however. The release in your patch is 1jpp%{?dist}. It should be 1jpp.1{?dist} at least, assuming 1jpp from JPackage was the base (if JPackage wasn't the base, please use 0jpp for now, until the naming scheme is reassessed). See http://fedoraproject.org/wiki/Packaging/JPackagePolicy for more information. I have approved your commit access to the package -- bouncing bug over to you.
Built [1]. Andrew: I'll trigger a scratch build of eclipse once new lucene is populated to the build roots. Will open a separate bug if it fails. [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=450087
(In reply to comment #8) > Built [1]. Andrew: I'll trigger a scratch build of eclipse once new lucene is > populated to the build roots. Will open a separate bug if it fails. It's not going to build. There's some other wacky JVM issue in rawhide that I haven't had time to track down. I wasn't so concerned with it building, but more with it actually working. We'll have to run the automated tests against it. I'll add that to my ever-growing TODO list.
Andrew: Honestly, I don't care at all. If Eclipse doesn't work it's not lucene's fault and thus not my business. But in case it's going to break somehow horribly, I can assist creating compat packages.
(In reply to comment #10) > Andrew: Honestly, I don't care at all. Then why are you doing this? If you don't care, don't bother with this.
Andrew: Trust me, I have no intention to break anything needlessly. The new lucene is required for OpenGrok, that's why is this report blocker of its review.
(In reply to comment #12) > Andrew: Trust me, I have no intention to break anything needlessly. The new > lucene is required for OpenGrok, that's why is this report blocker of its review. Ah, I didn't see the blocker. If Eclipse doesn't work with the new lucene we'll deal with the fallout later. As a side note: are you aware of repoquery? It can tell you what packages need other packages. It could have helped you with the tomcat issue (that was you, right?) and this one in determining what packages will be affected by version bumps. Cheers.
Yes, I used repoquery to see what is needed by lucene. What tomcat issue? It probably wasn't me.
(In reply to comment #14) > What tomcat issue? It probably wasn't me. I must be thinking of someone else, then. Carry on :)