https://bugzilla.redhat.com/show_bug.cgi?id=1263580
--- Comment #2 from Gerard Ryan <gerard(a)ryan.lt> ---
Hi Severin,
I had a quick look at this today (I couldn't spend enough time on it yet to
provide a fix though). I believe that the change will need to be made in
maven-indexer (another one of my packages).
What's happening is that maven-indexer (and eclipse-m2e-core) have not been
keeping up to date with lucene as aggressively as Fedora. In maven indexer,
this LUCENE_36 is a constant that comes from a class in lucene that has the
supported API versions. In 5.x, the 3.x API versions appear to have been
dropped, so that's why we're seeing this error.
There's an (as yet unreleased) commit in maven-indexer repo to update to a
newer version of lucene, I don't know why it hasn't been released yet (it has
been there for a while).
What we could do in Fedora is update to an unreleased version of maven-indexer
to get this patch, but then we might hit other issues (it might be unreleased
because there are things broken; or the interface that m2e-core uses has
changed; or anything else).
There's also a constant in that class, LATEST, which should always work. As you
suggest, we should probably change to use this, and I'll probably do this, once
I've fixed the actual issue. This would at least prevent this blocker from
appearing (although it might just mask other issues down the line).
Thanks for reporting,
Gerard.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=4tb6SF8L3H&a=cc_unsubscribe