Hi, That’s my question about stage: in feature boot, you can define feature started before other.
For instance: featuresBoot=(…, wrap), myfeature Regards JB > Le 21 févr. 2021 à 15:04, Steinar Bang <[email protected]> a écrit : > >>>>>> Steinar Bang <[email protected]>: >>>>>> Steinar Bang <[email protected]>: > >>> But I had a thought waking up today: > >>> The reason it works when running locally is probably that the >>> troublesome jar file in the stack trace is already in my >>> $HOME/.m2/repository/ before I and the reason it fails in docker, is >>> probably that it starts with an empty $HOME/.m2/repository/ > > I have a new hypothesis now: > > wrap is loaded as a part of featuresBoot and that means in a regular > karaf that wrap will be loaded when one starts installing. > > However, in docker the application is added to featuresBoot, and this > means that wrap may not be loaded when the application loads. > > The feature that loads the failing non-bundle jar is shiro-web and the > shiro-web feature doesn't contain > <feature prerequisite='true'>wrap</feature> > > @JB Question 1: would it have helped if shiro-web required wrap? > > @JB Question 2: could it be an idea to have an "applicationBoot" set of > features that are loaded after featuresBoot have completed? >
