Thanks, Eric!
I'll study your config builders.
However, what I ended up doing in this case, was very simple: I
created a dummy users.properties file, and dropped it into the
src/test/resources/etc/ directory of the maven project for the pax exam
test:
Hi Steinar, for my Pax Exam Karaf tests, I am using a builder-style class I
wrote called KarafConfigurator for building the list of configuration
options.
It has methods for replacing bundled config files with user
supplied versions. Here's an example using startup.properties:
public
> Steinar Bang :
>> A simple workaround is to include your own users.properties in the pax-exam
>> option.
> Thanks! I will look into this.
I tried this:
@Configuration
public Option[] config() {
final MavenArtifactUrlReference authserviceFeatureRepo = maven()
> Jean-Baptiste Onofre :
> Hi,
> It’s has been discussed on the mailing list already (I don’t remember who
> reported this).
> The change we did is that etc/users.properties has the karaf user commented
> now (for security reason).
Right. I noticed yesterday, when rolling the .deb package
Hi,
It’s has been discussed on the mailing list already (I don’t remember who
reported this).
The change we did is that etc/users.properties has the karaf user commented now
(for security reason).
However, etc/users.properties is still part of the karaf distribution. But, as
it contains only
When I bumped the karaf version (affects the karaf-maven-plugin, the
karaf BoM and the pax exam tests in my project builds), then the pax
exam tests fail with this message:
[ERROR]
initializationError(no.priv.bang.authservice.tests.AuthserviceIntegrationTest)
Time elapsed: 0.015 s <<< ERROR!
