[ https://issues.apache.org/jira/browse/MNG-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petr Široký updated MNG-7661: ----------------------------- Description: I noticed there is a quite a few build (from Maven) and also compiler warnings (e.g. using deprecated verifier APIs) when running the integration tests. I noticed following: * {{maven-plugin-plugin}} complains about Maven deps which should be in {{provided}} scope {code:java} [INFO] --- maven-plugin-plugin:3.6.4:descriptor (default-descriptor) @ maven-it-plugin-bootstrap --- [ERROR] Some dependencies of Maven Plugins are expected to be in provided scope. Please make sure that dependencies listed below declared in POM have set '<scope>provided</scope>' as well.The following dependencies are in wrong scope: * org.apache.maven:maven-plugin-api:jar:3.8.6:compile * org.apache.maven:maven-model:jar:3.8.6:compile * org.apache.maven:maven-artifact:jar:3.8.6:compile * org.apache.maven:maven-core:jar:3.8.6:compile * org.apache.maven:maven-settings:jar:3.8.6:compile * org.apache.maven:maven-settings-builder:jar:3.8.6:compile * org.apache.maven:maven-builder-support:jar:3.8.6:compile * org.apache.maven:maven-repository-metadata:jar:3.8.6:compile * org.apache.maven:maven-model-builder:jar:3.8.6:compile * org.apache.maven:maven-resolver-provider:jar:3.8.6:compile {code} * several deprecated maven-verifier methods are being used (these are not being reported during being - I guess the warnings are disabled, but IDEA complains) {code:java} verifier.executeGoal( "process-sources" ); verifier.resetStreams(); verifier.addCliOption( "--settings" ); {code} * Jetty- WARN (related to the fact that the tests are using very old version, probably not a bad idea to upgrade that) {code:java} 26317 [qtp876069009-2062] WARN org.eclipse.jetty.util.ssl.SslContextFactory - EXCEPTION java.lang.UnsupportedOperationException: This method is deprecated and marked for removal. Use the getPeerCertificates() method instead. at java.base/javax.net.ssl.SSLSession.getPeerCertificateChain(SSLSession.java:295) at org.eclipse.jetty.util.ssl.SslContextFactory.getCertChain(SslContextFactory.java:1393) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:104) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:54) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:266) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.base/java.lang.Thread.run(Thread.java:833) {code} I would like to take a look at those and create small(ish) PRs with suggested fixes. was: I noticed there is a quite a few build (from Maven) and also compiler warnings (e.g. using deprecated verifier APIs) when running the integration tests. I noticed following: * {{maven-plugin-plugin}} complains about Maven deps which should be in {{provided}} scope {code:java} [INFO] --- maven-plugin-plugin:3.6.4:descriptor (default-descriptor) @ maven-it-plugin-bootstrap --- [ERROR] Some dependencies of Maven Plugins are expected to be in provided scope. Please make sure that dependencies listed below declared in POM have set '<scope>provided</scope>' as well.The following dependencies are in wrong scope: * org.apache.maven:maven-plugin-api:jar:3.8.6:compile * org.apache.maven:maven-model:jar:3.8.6:compile * org.apache.maven:maven-artifact:jar:3.8.6:compile * org.apache.maven:maven-core:jar:3.8.6:compile * org.apache.maven:maven-settings:jar:3.8.6:compile * org.apache.maven:maven-settings-builder:jar:3.8.6:compile * org.apache.maven:maven-builder-support:jar:3.8.6:compile * org.apache.maven:maven-repository-metadata:jar:3.8.6:compile * org.apache.maven:maven-model-builder:jar:3.8.6:compile * org.apache.maven:maven-resolver-provider:jar:3.8.6:compile {code} * several deprecated maven-verifier methods are being used (these are not being reported during being - I guess the warnings are disabled, but IDEA complains) {code:java} verifier.executeGoal( "process-sources" ); verifier.resetStreams(); verifier.addCliOption( "--settings" ); {code} * Jetty-related WARN (related to the fact that we the tests are using very old version, probably not a bad idea to upgrade that) {code:java} 26317 [qtp876069009-2062] WARN org.eclipse.jetty.util.ssl.SslContextFactory - EXCEPTION java.lang.UnsupportedOperationException: This method is deprecated and marked for removal. Use the getPeerCertificates() method instead. at java.base/javax.net.ssl.SSLSession.getPeerCertificateChain(SSLSession.java:295) at org.eclipse.jetty.util.ssl.SslContextFactory.getCertChain(SslContextFactory.java:1393) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:104) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:54) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:266) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.base/java.lang.Thread.run(Thread.java:833) {code} I would like to take a look at those and create small(ish) PRs with suggested fixes. > Fix IT build / compiler warnings > -------------------------------- > > Key: MNG-7661 > URL: https://issues.apache.org/jira/browse/MNG-7661 > Project: Maven > Issue Type: Task > Components: Integration Tests > Reporter: Petr Široký > Priority: Minor > > I noticed there is a quite a few build (from Maven) and also compiler > warnings (e.g. using deprecated verifier APIs) when running the integration > tests. > I noticed following: > * {{maven-plugin-plugin}} complains about Maven deps which should be in > {{provided}} scope > {code:java} > [INFO] --- maven-plugin-plugin:3.6.4:descriptor (default-descriptor) @ > maven-it-plugin-bootstrap --- > [ERROR] Some dependencies of Maven Plugins are expected to be in provided > scope. > Please make sure that dependencies listed below declared in POM > have set '<scope>provided</scope>' as well.The following dependencies are in > wrong scope: > * org.apache.maven:maven-plugin-api:jar:3.8.6:compile > * org.apache.maven:maven-model:jar:3.8.6:compile > * org.apache.maven:maven-artifact:jar:3.8.6:compile > * org.apache.maven:maven-core:jar:3.8.6:compile > * org.apache.maven:maven-settings:jar:3.8.6:compile > * org.apache.maven:maven-settings-builder:jar:3.8.6:compile > * org.apache.maven:maven-builder-support:jar:3.8.6:compile > * org.apache.maven:maven-repository-metadata:jar:3.8.6:compile > * org.apache.maven:maven-model-builder:jar:3.8.6:compile > * org.apache.maven:maven-resolver-provider:jar:3.8.6:compile > {code} > * several deprecated maven-verifier methods are being used (these are not > being reported during being - I guess the warnings are disabled, but IDEA > complains) > {code:java} > verifier.executeGoal( "process-sources" ); > verifier.resetStreams(); > verifier.addCliOption( "--settings" ); {code} > * Jetty- WARN (related to the fact that the tests are using very old > version, probably not a bad idea to upgrade that) > {code:java} > 26317 [qtp876069009-2062] WARN org.eclipse.jetty.util.ssl.SslContextFactory - > EXCEPTION > java.lang.UnsupportedOperationException: This method is deprecated and marked > for removal. Use the getPeerCertificates() method instead. > at > java.base/javax.net.ssl.SSLSession.getPeerCertificateChain(SSLSession.java:295) > at > org.eclipse.jetty.util.ssl.SslContextFactory.getCertChain(SslContextFactory.java:1393) > at > org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:104) > at > org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:54) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:266) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:224) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) > at java.base/java.lang.Thread.run(Thread.java:833) {code} > > I would like to take a look at those and create small(ish) PRs with suggested > fixes. > -- This message was sent by Atlassian Jira (v8.20.10#820010)