Maven implicit "exposed" dependencies not shown in "dependencies: tree"

A colleague is trying to create a new Spring project. The project is explicitly dependent on spring-security, which in turn (implicitly) is dependent on wss4j. When running tests, he has a problem with the missing class.

We are tracking the missing class for the -saj axis, the “provided” wss4j dependency. When I run the dependency:treemaven target , it is not listed as a dependency on its project.

My understanding of “provided” is as follows: it is allowed by Maven for assembly, but is not included in the supplied and not provided by Maven (on the way to classes) for any phases of “launch” (running tests and launching the application itself through Maven).

So, when the dependency is “provided” implicitly to your project, Maven completely ignores it, since it does not actually create a delivered product, which depends on the “provided” artifact, and it is up to you to provide it for launch, time.

I tested and dependency:treelisted the provided dependencies if they are explicit dependencies of your project, but not if they are lower in the dependency tree.

I told him to include the dependency as explicit (scoped 'runtime) at the moment, but it is obvious that this will cause problems in the complete runtime (it is not limited to “provided” for nothing), but we need to know the dependencies in order to explicitly include them . Does anyone know how to get a complete list of dependencies for a project?

thank

PS. , "-saaj" "", , - !

. Maven 3

PPPS. - pom, . , (groupId) org.springframework.ws, (artifactId) spring -ws-security, (version) 2.0.0.RELEASE.

+5
2

mvn dependency:tree mvn dependency:list " ", . , , , , "", - , , . , , , , . / , , , , .

+1

, axis-saaj optional=true?

, , , , , .

+2

All Articles