Custom exploded artifact
I am trying to add support for a custom artifact. Our code is broken into modules which have a well defined structure so I would like to be able to point fileinstall at the directory containing the modules and generate the manifest based on some rules (probably using bnd). I have tried registering an implementation of ArtifactTransformer and ArtifactUrlTransformer but I am confused about which I should use, and confused about weather exploded artifacts are supported (as changes outside the top directory do not always trigger the canHandle method. Also, the path I get is to data/generated-bundles, not deploy. I have also looked at the fileinstall source and karaf source but everything I have found relates to single files, not exploded directories. Can anyone give me pointers on how exploded artifacts in karaf work and what hooks I should use to generate the manifest? thanks, Thomas -- View this message in context: http://karaf.922171.n3.nabble.com/Custom-exploded-artifact-tp3119292p3119292.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: karaf shell history ( command line completion ) not working on linux
I no history between sessions and an empty ~/.karaf directory on linux (ubuntu) too. -- View this message in context: http://karaf.922171.n3.nabble.com/karaf-shell-history-command-line-completion-not-working-on-linux-tp2957256p2991948.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Disable automatic bundle restart?
I don't use an activator, the manifest has a Bundle-Module entry which a peaberry bundle uses to do the registration. The bundles aren't part of a feature. thanks, Thomas -- View this message in context: http://karaf.922171.n3.nabble.com/Disable-automatic-bundle-restart-tp2986102p2987793.html Sent from the Karaf - User mailing list archive at Nabble.com.
Disable automatic bundle restart?
Using peaberry, I have bundle A which exports a service and bundle B which uses the service. Using the vanilla felix installation I can restart bundle A and bundle B then uses the new instance. Under karaf, when I restart bundle A bundle B gets restarted too. Is this a karaf feature? Is there a way to switch off this feature? I am new to osgi so maybe there is a different way to do this. Essentially I am trying to find the best way to redeploy new code without disrupting the dependencies (with or without peaberry). Maybe services should never keep a reference to another service and lookup the service on every use? Any pointers would be appreciated. -- View this message in context: http://karaf.922171.n3.nabble.com/Disable-automatic-bundle-restart-tp2986102p2986102.html Sent from the Karaf - User mailing list archive at Nabble.com.
