Hi guys,
Sorry to jump in so late I was very busy (mostly with Apache Unomi release
:))
Having a build-time resolution would be indeed very interesting.
Also I love the idea of having simpler dependency error display, because
the current one with all the filters is really hard to read and understand,
even for seasoned OSGi devs. But I'm guessing that's in Felix no ?
I'm very impatient for the ENV variable feature as that one is really a
problem when building docker images, and currently we use a workaround in
Unomi that I don't really like (basically providing overrides for all the
properties manually !)
Thanks for all the hard work, I wish I could be more active directly in
Karaf but I'm already quite busy with my project :)
cheers,
Serge...
On Thu, May 7, 2020 at 5:39 AM Jean-Baptiste Onofre <j...@nanthrax.net> wrote:
> Hi Matt,
>
> Local repo is not a problem, but it doesn’t help a lot for resolution.
>
> The resolution state at build time would simplify and speed up a lot the
> bootstrapping.
>
> Regards
> JB
>
> > Le 6 mai 2020 à 20:05, Matt Pavlovich <mattr...@gmail.com> a écrit :
> >
> >
> >
> >> On May 6, 2020, at 10:45 AM, Steinar Bang <s...@dod.no> wrote:
> >>
> >>> 2. Improve build tool (part of devx) for build time resolution
> >>
> >> Hm... can this be used to fill up the system directory when creating a
> >> docker image on top of the official image?
> >>
> >
> > Have you looked at using local-repo? We’ve had good success copying
> artifacts into the local-repo to ship an all-in-one, vs applying on top of
> system. Not married to one way or the other, but might be good to talk it
> through as far as the default tooling behavior and if there is a suggested
> convention on what should be in “system/“ vs “local-repo/“.
> >
> > etc/org.ops4j.pax.url.mvn.cfg:
> > ...
> > file:${karaf.home}/local-repo@snapshots@id=karaf.local-repo
> >
> >
>
>
