Hi Nino,
For me, this work in assembly project structure :
putting configuration files in etc assembly source folder :
*assembly/src/main/resources/etc*
all files under this directory will be include by the karaf-maven-plugin.
François
Le 02/02/2018 à 14:11, nino martinez wael a écrit :
> Hi
For approach 2, it's explain in the documentation :
http://karaf.apache.org/manual/latest/#_maven_assembly
under the Minimal Dirstribution Example :
src/main/resources
false
**/*
Agree with François ;)
I spent time on the user guide to describe this.
Now, we are working on a way better dev guide.
Regards
JB
On 02/02/2018 12:03 PM, Francois Papon wrote:
> For approach 2, it's explain in the documentation :
> http://karaf.apache.org/manual/latest/#_maven_assembly
>
>
Hi Jean
I cannot share the project.. But I can give you some fragments:
Project structure (assembly)
https://imgur.com/a/c8RUG
C:.
└───main
├───distribution
│ └───text
│ └───etc
│ | -> dk.netdesign.dialer.cfg this is the config
file I want in etc
For a custom distro, you have two approaches:
- using the resource approach, where you have cfg file in a project resource
folder. For this you have to use the resources or assembly plugins for instance
(as execution step).
- using in features.xml used for the assembly, using the karaf plugin
Yeah so I must be doing something wrong, I know that.. And of course the
maven properties are parsed so project.version are replaced with the
correct stuff..
What about Approach 2 ? Are there any special steps needed? When putting
the config files into the etc folder for a custom distribtion?
Hi,
I confirm it works as it's what we are using in Decanter or Cellar, or even
Karaf itself.
1. configfile:
https://github.com/jbonofre/karaf-decanter/blob/master/assembly/src/main/feature/feature.xml#L48
Here the files will end into the etc folder when you feature is installed.
Of course,
Hi fellow karaflings
I want to either prepackage or install my configuration files into the etc
folder of karaf when my feature installs.
I've tried a couple of different approaches, which all fails :( They fail
in the way that the configuration gets bound to the bundles mvn coordinates
and are
