You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2022/08/05 09:20:00 UTC
[jira] [Resolved] (SLING-11512) Sanity check should check for updated releases/snapshots
[ https://issues.apache.org/jira/browse/SLING-11512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-11512.
-------------------------------------
Resolution: Fixed
> Sanity check should check for updated releases/snapshots
> --------------------------------------------------------
>
> Key: SLING-11512
> URL: https://issues.apache.org/jira/browse/SLING-11512
> Project: Sling
> Issue Type: Improvement
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Jenkins 'Sanity Check' stage runs a {{mvn clean compile}} command. In case this is run before artifacts have been published to Maven Central, the failure will be cached ( by default for a day according to https://maven.apache.org/ref/3.8.6/maven-settings/settings.html#releases ) . We should instead pass the "-U" flag to the command.
> I encountered this while validating https://github.com/apache/sling-org-apache-sling-starter/pull/73
--
This message was sent by Atlassian Jira
(v8.20.10#820010)