[
https://issues.apache.org/jira/browse/BEAM-11377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251329#comment-17251329
]
Kenneth Knowles commented on BEAM-11377:
----------------------------------------
The workspace-local .m2 wouldn't have any effect if it is wiped.
Snapshots are not an issue. They are not published under names like
{{beam-sdks-java-core-2.27.0-SNASHOT.jar}}. They are published with dated jars
like {{beam-sdks-java-core-2.27.0-20201210.070217-43.jar}} (see
https://repository.apache.org/content/groups/snapshots/org/apache/beam/beam-sdks-java-core/2.27.0-SNAPSHOT/).
The maven flag {{-U}} / {{--update-snapshots}} forces a check to see if there
is a newer one.
Oddly, in the console log it seems that we pass that flag for {{mvn
archetype:generate}} but not for {{mvn compile exec:java}}.
> beam_PostRelease_NightlySnapshot failing (connection reset fetching deps)
> -------------------------------------------------------------------------
>
> Key: BEAM-11377
> URL: https://issues.apache.org/jira/browse/BEAM-11377
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Kenneth Knowles
> Priority: P1
> Labels: flake
>
> https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/1195/
> {code}
> 03:05:12 [ERROR] Failed to execute goal on project word-count-beam: Could not
> resolve dependencies for project org.example:word-count-beam:jar:0.1: Failed
> to collect dependencies at
> org.apache.beam:beam-sdks-java-io-google-cloud-platform:jar:2.27.0-SNAPSHOT
> -> com.google.cloud:google-cloud-spanner:jar:2.0.2: Failed to read artifact
> descriptor for com.google.cloud:google-cloud-spanner:jar:2.0.2: Could not
> transfer artifact com.google.cloud:google-cloud-spanner:pom:2.0.2 from/to
> central (https://repo.maven.apache.org/maven2): Connection reset -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
