On Thu, 2015-09-03 at 09:59 +0200, Julian Reschke wrote: > On 2015-09-03 09:14, Robert Munteanu wrote: > > On Wed, 2015-09-02 at 18:35 +0000, Tomek Rekawek wrote: > > > Hi, > > > > > > One more thing. The “upgrade" command requires a lot of Maven > > > dependencies (Amazon API client for the S3 support, Jackrabbit 2 > > > for > > > the repository upgrades, etc.) Some of these dependencies > > > conflicts > > > with the Oak modules (eg. Jackrabbit 2 uses older lucene-core > > > than > > > the oak-lucene and the new version is not backward-compatible). > > > Because of that, the dependency management in the oak-run module > > > is > > > complicated - even before my patch there is a separate profile > > > for > > > building the project using Jackrabbit 2 dependencies and there > > > are > > > also two assembly files building the normal jar and the > > > “jackrabbit > > > 2” jar. > > > > Without being familiar with the codebase, it sounds like it's a > > good > > candidate oak-run being based on OSGi. Classpath incompatibilities > > should be solved in a more elegant manner and we can also benefit > > from > > all the OSGi goodies. > > > > Robert > > oak-run must be usable for emergency repairs, thus please be careful > with new dependencies.
Ack. _If_ we decide OSGi, it must be embedded and controlled by the oak -run instance, and not a general-use OSGi application like e.g. Karaf with some bundles added. Robert
