We are using org.codehaus.mojo.wagon 2.0.0. Is there a newer one? Looking at that pom, we might be able to upgrade its wagon plugins by adding -Dwagon.api.version=3.4.0 to the command line.
It might be a better use of time to try to get the upload to run from the CI server. -Alex On 4/28/20, 11:47 PM, "Christofer Dutz" <[email protected]> wrote: Apache Wagon is the provider .... not the plugin. I think you might need to use the newest version of the wagon-maven-plugin and replace the wagon provider by excluding the old and adding a dependency to the new. The thing is that wagon is actually the logic used internally by all sorts of maven subsystems. It's used for dependency download and upload, version detections etc. The wagon-maven-plugin is just a small wrapper plugin around the wagon core to allow to do some of the stuff using the API directly. And regarding Infra ... no problems were known to them with regards to service outages or extended unresponsiveness. Chris Am 29.04.20, 08:24 schrieb "Yishay Weiss" <[email protected]>: 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=DMXCn%2Bf4P%2BO2UKmUH5aBd1UmK6ipNeCM2rxZ730FdQU%3D&reserved=0 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepo.maven.apache.org%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=DMXCn%2Bf4P%2BO2UKmUH5aBd1UmK6ipNeCM2rxZ730FdQU%3D&reserved=0 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=cn3NaVbC1ciFWG816GFvky0cmUL0VatGNi5hy2sB6JY%3D&reserved=0</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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=cn3NaVbC1ciFWG816GFvky0cmUL0VatGNi5hy2sB6JY%3D&reserved=0</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%7Cb703c63548a440486dfb08d7ec092066%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237396255828787&sdata=e6PhAhwBJhZvoMzzNd3030maMIVOUkegGvMyOeMZlPE%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"/>
