The oak-lucene module exposes an api that is oak specific and doesn't contain any lucene package names, but it uses lucene internally. Shading the lucene jar translates the package names so instead of having names like org.apache.lucene, they are called prefix.org.apache.lucene etc. The oak-lucene implementing classes also change their import to import prefix.org.apache.lucene.
So any other code in your project can now use a newer version of lucene, since there's no jars in your project otherwise that have classes with package names org.apache.lucene. On Wed, 13 May 2020 at 15:30, KÖLL Claus <[email protected]> wrote: > > You are right it was requested years ago .. I think it's work but not > impossible .. hopefully :-) > > Maybe i do not understand your idea .. What ist the plan with a shaded jar > file ? > How would it help to upgrade to a newer version ? > > thanks > claus > > >I understand what you'd like to do, but there's a reason it hasn't > >happened yet. It was requested many years ago, and it's not easy. > -- -Tor
