Le 17/01/2018 à 23:32, Steinar Bang a écrit :
> Is pulling the jars in from maven central from maven depdencies
> acceptable? Or do they need to be acually built by the packaging
> project?
It's ok at run time but not at build time (the packages are built in
offline mode).
Emmanuel Bourg
> Emmanuel Bourg :
> Le 17/01/2018 à 22:44, Steinar Bang a écrit :
>> Would be legal for a karaf debian package to bundle its own version of
>> these jars?
> It's fine as long as they are built from source (i.e. no prebuilt jar
> files in the source package),
Is pulling the jars in from mave
Le 17/01/2018 à 22:44, Steinar Bang a écrit :
> Would be legal for a karaf debian package to bundle its own version of
> these jars?
It's fine as long as they are built from source (i.e. no prebuilt jar
files in the source package), but you should really try to package them
separately or use the
Le 17/01/2018 à 18:33, Steinar Bang a écrit :
> If I pick something other than 4.5.0, it's no longer karaf 4.1.4 but
> something slightly different.
Yes you are right, and it can lead to subtle issues but this is a risk
we accept for the convenience of maintaining only one version of a
library. F
One property of karaf: it can load its dependencies using maven.
Ie. it will download its dependencies to ~/.m2/repository and use it
from there. It doesn't have to be provided by other debian packages.
The question is: how much must be in place for karaf to boot far enough
to start loading file
> Thorsten Glaser :
>> Do you have a compatibility issue with libjna-java?
> … those.
I used it as an example since it's part of the boot set of apache karaf,
which in karaf 4.1.4, is:
-rw-r--r-- 1 sb sb 1440500 Dec 15 20:14 jna-4.5.0.jar
-rw-r--r-- 1 sb sb 2324986 Dec 15 20:14 j
6 matches
Mail list logo
