Yes, I was referring to the tooling. Specifically, does it make sense for
tooling to use local-repo for application coded artifacts, vs system/ which
seems to be for karaf itself.
> On May 6, 2020, at 10:40 PM, 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
>>
>>
>
