In a Maven plugin project, I use the Maven Core API and also maven-plugin-testing-harness 3.3.0. It looks as if the testing harness at some point wans to access Plexus Cipher and then while running tests with Surefire, it throws:
java.lang.ClassNotFoundException: org.sonatype.plexus.components.cipher.PlexusCipherException If I compare the dependency trees of Maven Core between 3.8.1 and 3.8.2, I see: +- org.apache.maven:maven-core:jar:3.8.1:provided | +- org.apache.maven:maven-settings:jar:3.8.1:compile | +- org.apache.maven:maven-settings-builder:jar:3.8.1:compile | | \- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile | | \- org.sonatype.plexus:plexus-cipher:jar:1.4:compile Versus: +- org.apache.maven:maven-core:jar:3.8.2:provided | +- org.apache.maven:maven-settings:jar:3.8.2:compile | +- org.apache.maven:maven-settings-builder:jar:3.8.2:compile | | \- org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:compile In 3.8.2, Plexus Cipher is defined in the Maven Core POM as a test-scoped dependency. This seems to lead to the effect of it not being found by the test harness class. The workaround to add Plexus Cipher as a direct dependency to my plugin project works, but my own classes do not depend on it, so dependency:analyze would always report it as a declared but unused dependency, and rightly so. Please advise me what I should do: File an issue? If so, in which Jira project? -- Alexander Kriegisch https://scrum-master.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
