Not sure if this is a good idea. This way the test is quite different
from your real system.
Better use editConfigurationFilePut to create the data source config you
need for the test.
Christian
On 20.04.2017 16:18, Matteo Rulli wrote:
Thank you Christian. Yes you are right, we could simply
Thank you Christian. Yes you are right, we could simply avoid to embed the
config placeholders in the feature file.
But there is also another way that just came to my mind:
Option[] options = new Option[] {
editConfigurationFilePut( "etc/config.properties",
"felix.fileinstall.poll",
I think there is or was an issue with loading factory configs as
defaults in a feature.
As your database config normally contains secret information I propose
to not install it in the feature. Instead you can deploy the config as
part of your pax exam setup.
Christian
On 20.04.2017 12:09,
Hello,
We are running a couple of integration tests using pax-exam 4.10.0 and Karaf
4.0.8. In the test's @Configuration method we install a feature that contains
both the bundle under test and the corresp. configuration files.
The tests work fine on most dev machines except one where the test
