I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the
pom.xml entry according to Alex’s suggestion but I’m getting
[exec] [DEBUG] Resolving plugin prefix wagon from
[org.apache.maven.plugins, org.codehaus.mojo]
[exec] [WARNING] Failed to retrieve plugin descriptor for
org.apache.maven.wagon:wagon:3.4.0: Plugin org.apache.maven.wagon:wagon:3.4.0
or one of its dependencies could not be resolved: Failure to find
org.apache.maven.wagon:wagon:jar:3.4.0 in https://repo.maven.apache.org/maven2
was cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced
[exec] org.apache.maven.plugin.PluginResolutionException: Plugin
org.apache.maven.wagon:wagon:3.4.0 or one of its dependencies could not be
resolved: Failure to find org.apache.maven.wagon:wagon:jar:3.4.0 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced
From: Alex Harui<mailto:[email protected]>
Sent: Tuesday, April 28, 2020 8:09 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if
wagon fails
We are currently using org.codehaus.mojo's wagon-maven-plugin 2.0.0.
There is an org.apache.maven.wagon.Wagon that is at 3.4.0. I think we can
switch to that by replacing the wagon entry in the royale-asjs pom.xml
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>wagon-maven-plugin</artifactId>
<version>2.0.0</version>
<configuration>
<includes>**</includes>
<serverId>apache.releases.https</serverId>
<url>https://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
Would become something like:
<plugin>
<groupId>org.apache.maven.wagon </groupId>
<artifactId>wagon</artifactId>
<version>3.4.0</version>
<configuration>
<includes>**</includes>
<serverId>apache.releases.https</serverId>
<url>https://repository.apache.org/service/local/staging/deploy/maven2</url>
</configuration>
</plugin>
HTH,
-Alex
On 4/27/20, 1:46 PM, "Alex Harui" <[email protected]> wrote:
Don't see Wagon 3.4.0 on Central. I do see Wagon Providers 3.4.0. How
would we get the Wagon we use to use Wagon Providers?
When the upload fails, Yishay is not given a away to start from the point
of failure ("maven -rf ..."). I have suggested using Wagon to upload
individual folders
-Alex
On 4/27/20, 3:07 AM, "Christofer Dutz" <[email protected]> wrote:
Hi all,
a week ago a new version of Wagon was released ... perhaps worth
updating to 3.4.0?
Chris
Am 27.04.20, 11:58 schrieb "Yishay Weiss" <[email protected]>:
Awesome
________________________________
From: [email protected] <[email protected]>
Sent: Monday, April 27, 2020 8:56:00 AM
To: [email protected] <[email protected]>
Subject: [royale-asjs] branch release/0.9.7 updated: add retry task
if wagon fails
This is an automated email from the ASF dual-hosted git repository.
aharui pushed a commit to branch release/0.9.7
in repository
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.git&data=02%7C01%7Caharui%40adobe.com%7Cf93a7122d006493a7cf808d7eaec147b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637236172044662963&sdata=uG%2FjLtaz1c%2BTaDvApclw%2Bihx5sXhm1QxQBoU91otykM%3D&reserved=0
The following commit(s) were added to refs/heads/release/0.9.7 by
this push:
new adeb2e3 add retry task if wagon fails
adeb2e3 is described below
commit adeb2e3782b59342d9132adccaf357aeece32475
Author: Alex Harui <[email protected]>
AuthorDate: Sun Apr 26 22:55:41 2020 -0700
add retry task if wagon fails
---
releasesteps.xml | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/releasesteps.xml b/releasesteps.xml
index 729a6fc..d0f3f0a 100644
--- a/releasesteps.xml
+++ b/releasesteps.xml
@@ -836,6 +836,23 @@
<arg value="_releasesteps-upload-release-to-staging" />
</exec>
</target>
+ <target name="retryUploadSWCs" depends="get-artifact-folder"
description="upload all SWCs except Jewel Themes">
+ <fail message="release.version not specified"
+ unless="release.version"/>
+ <fail message="rf_arg not specified"
+ unless="rf_arg"/>
+ <exec executable="${mvn}" dir="${artifactfolder}/sources"
failonerror="true" >
+ <arg value="wagon:upload" />
+ <arg value="-X" />
+ <arg value="-rf" />
+ <arg value="${rf_arg}" />
+ <arg
value="-Dwagon.fromDir=${artifactfolder}/artifacts/archive/target/local-release-dir"
/>
+ <!--arg value="-Dwagon.includes=**" />
+ <arg
value="-Dwagon.excludes=**/Jewel-Dark*/**,**/Jewel-Light*/**" /-->
+ <arg value="-P" />
+ <arg value="_releasesteps-upload-release-to-staging" />
+ </exec>
+ </target>
<target name="uploadJewelDark" depends="get-artifact-folder"
description="upload Jewel Dark Themes">
<fail message="release.version not specified"
unless="release.version"/>
