java - Maven dependency management issue -


i have multi pom project, parent pom imports external module such. external module uses saxon classes, import such:

        <dependency>             <groupid>org.test</groupid>             <artifactid>test-framework</artifactid>             <version>1.0-snapshot</version>         </dependency> 

in child pom, import such:

    <dependency>         <groupid>org.test</groupid>         <artifactid>test-framework</artifactid>         <scope>provided</scope>     </dependency> 

i under impression if imported such in parent pom, transitive dependencies of external module imported. when i'm building project saxon classes missing , way can them appear explicitly pull them down in pom. doesn't defeat point of transitive dependency resolution. going have explicitly pull down transitive dependencies in project imports external module?

have tried changing scope of dependency?

<dependency>     <groupid>org.test</groupid>     <artifactid>test-framework</artifactid>     <scope>compile</scope> </dependency> 

this should job.

read on dependency scopes here:

https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#dependency_scope


Comments

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - Cannot secure connection using TLS -