Re: oak-run upgrade improvements

2015-09-03 Thread Robert Munteanu
On Wed, 2015-09-02 at 18:35 +, 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.

Re: oak-run upgrade improvements

2015-09-03 Thread Robert Munteanu
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 +, Tomek Rekawek wrote: > > > Hi, > > > > > > One more thing. The “upgrade" command requires a lot of Maven > > > dependencies (Amazon API client for the S3

Re: oak-run upgrade improvements

2015-09-03 Thread Julian Reschke
On 2015-09-03 09:14, Robert Munteanu wrote: On Wed, 2015-09-02 at 18:35 +, 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

Re: oak-run upgrade improvements

2015-09-03 Thread Bertrand Delacretaz
On Thu, Sep 3, 2015 at 10:01 AM, Robert Munteanu wrote: > ... _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... Note that Sling's slingstart-maven-plugin

Re: oak-run upgrade improvements

2015-09-02 Thread Tomek Rekawek
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