oak-parent: DB2 dependency with system scope

[Julian Reschke <ju...@gmx.de>]

Hi,

we currently have a system-scoped dependency for the DB2 JDBC drivers, 
because (by copyright) they are not available from Maven repos.

Turns out that this doesn't work well with the Maven Shade plugin, which 
is used to build oak-run.

It seems the path of least resistance is to make the DB2 dependency a 
regular one, and require those who need it to deploy the JARs to their 
local Maven repo.

Can everybody live with that?

Best regards, Julian

Re: oak-parent: DB2 dependency with system scope

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Jun 12, 2014 at 9:36 AM, Julian Reschke <ju...@gmx.de> wrote:
> thanks; I'm going with option 1); it's a bit messy but then it only affects
> people who want to test with DB2 for now.

An alternative with different messiness aspects would be to place the
DB2 driver in $JAVA_HOME/lib/ext.

BR,

Jukka Zitting

Re: oak-parent: DB2 dependency with system scope

[Julian Reschke <ju...@gmx.de>]

On 2014-06-12 07:35, Chetan Mehrotra wrote:
> Instead of embedding various such drivers I would prefer we
> include/refer them as part of classpath on command line. So one of the
> following two approaches can be used
>
> 1. Specify the jars as part of classpath
>
> java -cp oak-run-xxx.jar:driver.jar org.apache.jackrabbit.oak.run.Main
> benchmark ...
>
> 2. OR refer to the jars (pre defined names) as part of Class-Path
> attribute of oak-run manifest and place the required jars in same
> directory. In that can you can just run the jar with java -jar
>
> Chetan Mehrotra
> ...

Chetan,

thanks; I'm going with option 1); it's a bit messy but then it only 
affects people who want to test with DB2 for now.

Best regards, Julian

Re: oak-parent: DB2 dependency with system scope

[Chetan Mehrotra <ch...@gmail.com>]

Instead of embedding various such drivers I would prefer we
include/refer them as part of classpath on command line. So one of the
following two approaches can be used

1. Specify the jars as part of classpath

java -cp oak-run-xxx.jar:driver.jar org.apache.jackrabbit.oak.run.Main
benchmark ...

2. OR refer to the jars (pre defined names) as part of Class-Path
attribute of oak-run manifest and place the required jars in same
directory. In that can you can just run the jar with java -jar

Chetan Mehrotra


On Wed, Jun 11, 2014 at 11:09 PM, Julian Reschke <ju...@gmx.de> wrote:
> Hi,
>
> we currently have a system-scoped dependency for the DB2 JDBC drivers,
> because (by copyright) they are not available from Maven repos.
>
> Turns out that this doesn't work well with the Maven Shade plugin, which is
> used to build oak-run.
>
> It seems the path of least resistance is to make the DB2 dependency a
> regular one, and require those who need it to deploy the JARs to their local
> Maven repo.
>
> Can everybody live with that?
>
> Best regards, Julian