>>>>> Steinar Bang <[email protected]>:
>>>>> Steinar Bang <[email protected]>:

>> Platform:
>> debian 9.6 "stretch",
>> openjdk-8 8u181-b13-2~deb9u1,
>> maven 3.3.9,
>> pax exam 4.10.0

>> When I add some maven dependencies with <scope>provided</scope>, without
>> changing anything else, my karaf-based pax exam test starts failing.  

>> Is this expected? 

> To condense my question: is there a way adding two provided scope
> dependencies to the <dependencies> element of the POM, could affect the
> pax exam container startup?

A transient dependency to nekohtml:nekohtml:jar:0.9.5:compile was what
stopped karaf before it startet loading features.

When the added dependencies looked like this, the pax exam test ran
wothout failure:
        <dependency>
            <groupId>com.mockrunner</groupId>
            <artifactId>mockrunner-core</artifactId>
            <scope>provided</scope>
            <exclusions>
                <exclusion>
                    <groupId>nekohtml</groupId>
                    <artifactId>nekohtml</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>com.mockrunner</groupId>
            <artifactId>mockrunner-servlet</artifactId>
            <scope>provided</scope>
            <exclusions>
                <exclusion>
                    <groupId>nekohtml</groupId>
                    <artifactId>nekohtml</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>com.mockrunner</groupId>
            <artifactId>mockrunner-servlet</artifactId>
            <version>${mockrunner.version}</version>
            <type>xml</type>
            <classifier>features</classifier>
        </dependency>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to