-
Type:
Technical task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: upgrade
-
Labels:None
Tomek Rękawek in OAK-7686 noted [0] that it's non trivial to include current lucene jar in oak-upgrade because it already includes jackrabbit-core (which, in turn, bring with itself old lucene version).
There are at least 2 different ways to handle this:
- shade out lucene classes while embedding jackrabbit-core - afaict, oak-upgrade only depends on logic in jackrabbit-core that reads old jackrabbit repositories
- create a separate oak-upgrade for upgrading from old jackrabbit repository... for "normal" oak-upgrade, we can then embed lucene jar without issues