RE: KAR deployment

Hi Stephen, I played around with KAR’s for quite a while with similar issues. I ended up ditching them in favour of the karaf feature deployment. This is far simpler and cleaner than kar. It does require that you have your dependencies / bundles available in an accessible maven repo from your

Fwd: KAR deployment

I'm having a small problem constructing a KAR file. Basically, I have a pom with the type set to KAR. The maven plugin generates a KAR file, which contains some of the libraries, specifically my OSGI bundles and their dependencies. The problem is that the requirements specified in the feature

Re: vaadin 8 wrapped jar dependency doesn't go active

> Steinar Bang : > It seems like 1.2.0.vaadin1 can be fetched from maven central, so I > won't need to set up an extra repo: > karaf@root()> bundle:install mvn:com.vaadin.external/gentyref/1.2.0.vaadin1 > Bundle ID: 127 > karaf@root()> bundle:list > START LEVEL 100 , List

Re: vaadin 8 wrapped jar dependency doesn't go active

> Steinar Bang : > Christian Lutz : >> Your bundle doesnt have version specified >>> Bundle-Version: 0 >> To fix this you need to add the bundle-version to your wrap like >> wrap:mvn:com.googlecode.gentyref/gentyref/1.2.0=1.2.0 > Right! I wondered

Re: vaadin 8 wrapped jar dependency doesn't go active

> : > Hi. > Vaadin 8.1.4 uses gentyref version 1.2.0.vaadin1. I included that in my > feature. Maybe working for 8.1.5 as well. > > http > http-whiteboard > mvn:org.jsoup/jsoup/1.8.3 >

Re: Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

> You can implement your own PersistenceManager (ConfigAdmin service). OK, I'm actually super confused now (not hard). felix configadmin appears to have logic in it that persists configurations to and from files. It's unclear in the karaf environment where the FilePersistenceManager is

Re: Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

You could also look at the read-only implementation of ConfigAdmin we have in Karaf. That can easily be used to remove fileinstall completely, as done in the static configurations. https://github.com/apache/karaf/tree/master/services/staticcm/src/main/java/org/apache/karaf/services/staticcm

Re: Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

Hi Tom, You can implement your own PersistenceManager (ConfigAdmin service). Regards JB On 10/06/2017 01:07 PM, t...@quarendon.net wrote: I can see KARAF-418, but that's pretty old, and sounds like it was considered unnecessary? Is there anything else I can't find? I don't necessarily want

Re: Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

I can see KARAF-418, but that's pretty old, and sounds like it was considered unnecessary? Is there anything else I can't find? I don't necessarily want to store things in a database, I just want different behaviour to normal, to provide my own implementation of something that listens to

Re: FW: Bundle third party feature repositories in KAR

Hmmm The XML should be embedded. If not, it's a bug. Let me try. Regards JB On Oct 6, 2017, 12:38, at 12:38, Liam MacIsaac wrote: >I'm trying to create a KAR file for offline installation of our project >using the maven plugin. I'm successfully got a KAR,

Re: Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

Hi I guess you want to use an alternative backend to the filesystem (a database for instance). In that case we have a Jira about that and you can provide your own persistence backend. Regards JB On Oct 6, 2017, 12:30, at 12:30, t...@quarendon.net wrote: >I'm trying to establish some

FW: Bundle third party feature repositories in KAR

I'm trying to create a KAR file for offline installation of our project using the maven plugin. I'm successfully got a KAR, but my feature file has two repository entries for CXF and activemq, the contents of which don't get embedded in the KAR, so karaf attempts to go to maven central to find

Providing alternative config mechanism than felix.fileinstall/Preserving config changes on re-install

I'm trying to establish some alternative configuration behaviour than what felix-fileinstall gives me. I have written a very simple component that reads configuration files in from /etc and updates config admin with the information, much like fileinstall does. I can run this and it appears to

Antw: Re: vaadin 8 wrapped jar dependency doesn't go active

Hi. Vaadin 8.1.4 uses gentyref version 1.2.0.vaadin1. I included that in my feature. Maybe working for 8.1.5 as well. http http-whiteboard mvn:org.jsoup/jsoup/1.8.3 mvn:com.vaadin.external/gentyref/1.2.0.vaadin1