Hello.
Thanks for your explanation. I didn't know this subtle limitation in
configuration files naming.
Regards.
Ephemeris Lappis
Le 09/08/2022 à 18:34, Jean-Baptiste Onofré a écrit :
Hi,
it's normal: PID is for configuration, in the case of a factory it's
different. A factory is using -.
Hi,
It's not easy to answer without a trace for instance or test case.
Can you share more details ?
Thanks,
Regards
JB
On Mon, Aug 8, 2022 at 9:36 AM Ephemeris Lappis
wrote:
>
> Hello.
>
> I'm trying to make a POC for refactoring old projects running today on
> Red-Hat Fuse, and thus using its
Hi,
it's normal: PID is for configuration, in the case of a factory it's
different. A factory is using -.
You should not use - in the name of a configuration (if it's not a factory).
Regards
JB
On Tue, Aug 9, 2022 at 12:09 PM Ephemeris Lappis
wrote:
>
> Hello.
>
> It seems that a
Hi,
Generating automatically a feature is basic approach.
Using this approach, you can use a template file if you want to use
more complex features set.
FYI, in Karaf, we don't generate the features XML (only the standard
one with template): we write all features XML by hand to have fully
Hi,
It's not a bug for two reasons:
1. If you absolutely need the config first, you can define a feature
with the configuration and use prerequisite=true
2. Generally speaking a bundle should be able to deal with
configuration update (basically a ManagedService instead of retrieving
config
Hello.
It seems that bundles that come from an installed feature are started
before the configuration file is installed.y
My feature example XML :
http://karaf.apache.org/xmlns/features/v1.6.0;
name="my-test-26-karaf-2-routes">
karaf-test :: Camel routes
Hello.
You're right, dependencies in scope "provided" are ignored (not
included as bundles), useful for dependencies that are needed at build
time, but are provided by features.
Dependencies in scope "compile" (default), are included as expected
when the plugin works.
For me it works now in two
> Ephemeris Lappis :
> Hello again !
> Well, it works better (yes !!!) : I had to change my packaging to
> "pom" instead of "feature", and to add an execution block with a goal
> "features-generate-descriptor" to trigger the plugin.
> Now it takes the template that declares dependent
> Ephemeris Lappis :
> Hello.
> I've tried using such a template, and all the elements from it are
> used, with filtering to generate the result file, but maven
> dependencies are not added as bundles to my feature.
> It seems that using the template makes the plugin ignore bundles
> Steven Huypens :
> Hi Steinar,
> As far as I can tell, there is a spifly-issue, which is why Liquibase
> cannot create the correct Log Services. I tried
> version="${liquibase.version}">
> aries-proxy
> mvn:org.apache.aries.spifly/org.apache.aries.spifly.dynamic.bundle/1.3.4
Hello.
It seems that a persistent-id for a configuration is not taken into
account if its name contains one or more "-" (dash).
For example, "my-test-26-karaf-2-routes" (my artifactId in fact) is
ignored, while "my_test_26_karaf_2_routes" is right.
I use Karaf 4.4.1...
Is it a bug or is it a
Hello again !
Well, it works better (yes !!!) : I had to change my packaging to
"pom" instead of "feature", and to add an execution block with a goal
"features-generate-descriptor" to trigger the plugin.
Now it takes the template that declares dependent features, filtering
properties values for
Hello.
I've tried using such a template, and all the elements from it are
used, with filtering to generate the result file, but maven
dependencies are not added as bundles to my feature.
It seems that using the template makes the plugin ignore bundles dependencies.
I've tried separating
13 matches
Mail list logo
