adoroszlai opened a new pull request, #2: URL: https://github.com/apache/tomcat-tck/pull/2
## What changes were proposed in this pull request? Fix repository definitions: 1. prefer `central`, not `repository.apache.org` 2. `asf-snapshots` does not have release artifacts ## How was this patch tested? Local build: ``` $ mvn -DskipTests clean package ... [INFO] Reactor Summary for tck 12.0.0-SNAPSHOT: [INFO] [INFO] tck ................................................ SUCCESS [ 0.071 s] [INFO] download ........................................... SUCCESS [ 29.008 s] [INFO] annotations-tck .................................... SUCCESS [ 7.930 s] [INFO] el-tck ............................................. SUCCESS [ 2.357 s] [INFO] jsp-tck ............................................ SUCCESS [ 9.348 s] [INFO] servlet-tck ........................................ SUCCESS [ 1.820 s] [INFO] websocket-tck ...................................... SUCCESS [ 0.786 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS ``` Repo list: ``` $ mvn -N --batch-mode eu.maveniverse.maven.plugins:toolbox:list-repositories ... [INFO] --- toolbox:0.6.0:list-repositories (default-cli) @ tck --- [INFO] Remote repositories used by project org.apache.tomcat:tck:pom:12.0.0-SNAPSHOT. [INFO] * central (https://repo.maven.apache.org/maven2/, default, releases) [INFO] First introduced on root [INFO] * asf-snapshots (https://repository.apache.org/content/groups/snapshots/, default, snapshots) [INFO] First introduced on root [INFO] * asf-staging (https://repository.apache.org/content/groups/staging/, default, releases+snapshots) [INFO] First introduced on root [INFO] * jakarta-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/, default, releases+snapshots) [INFO] First introduced on root [INFO] * jboss (https://repository.jboss.org/nexus/content/repositories/releases/, default, releases+snapshots) [INFO] First introduced on root ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
