Ah, I see… the service wrapper is a pain, requiring manual intervention every time, we do not activate for the CI. Do you really need it to run integration tests?
Best regards, Alex soto > On Nov 21, 2017, at 10:20 AM, smunro <stephen.ross.mu...@gmail.com> wrote: > > Hello Alex, > > I have disabled going to the remote repos on karaf which is fine so far. > > The CI server will build all the required packages and execute a feature > install. The problem with the karaf-assembly task is that I need to use a > custom karaf. Basically in my artefact repo, I have a karaf with the windows > service wrapper and all the service installer files generated. I want to > download this file, install the required features and bundle it up. I can't > seem to do that viathe plugin as far as I can see, so I've done it before > hand and stored karaf on a remote repo. > > I'm not sure if the feature:install issue is related to the remote access. > The problem is that on the CI server, I've installed the features (i.e > activemq) and some paths have been created referring to this machine and > when I try this on a client's machine, the logs complain that the classpath > cannot be resolved, with the path specifying the CI server machine it was > built on. > > Stephen > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
