The purpose of the CI build is to create an NSIS installer for the customer.
So, the installer contains karaf along with the service wrapper. The
Installer will put karaf in a standard place and kick off the service.
I've pretty much exhausted every approach on the karaf documentation and hit
multiple obstacles.
I seem to have gotten further packaging up karaf and putting it on nexus,
but as I said, when I extract it on the machine and execute feature:install,
the customer's logs show references to the build server path. I can't find
any references to that path when I scan the karaf installation, so I have no
idea if it's even possible to override. It would probably be idea if
relative paths were used to get round this issue.
Previously I tried to use the KAR, but that seems even trickier than
karaf-assembly.
So the goal is to have (1) A karaf installation with the windows service
wrapper setup
(2) All offline resources packaged.
I think I've burned up two weeks on finding a way to get this working and
I'm thinking of trying out a few other osgi containers to see if there is
better offline install support. It just feels like such a trivial task and
I've burned up too much time getting it to work (and failing).
I suppose I could do the windows service wrapper installation on the CI
service, but again, when I tried this on my desktop, I found paths were
absolute and I had to create a path that reflected where it would go on the
customer's machine.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
