So to me, a good test would be to copy all of the .asc files to the internet somewhere else. Push them all to a git repo, or to dropbox or some other cloud storage via a git command or a script. Because if that works for you, it really points the finger at some aspect of Windows networking not communicating well with the staging server.
Also, is it really "hanging" as in you have to kill maven or does it just fail at some point? And if it fails does it give you the option to continue where it failed? -Alex On 4/29/20, 10:05 AM, "Yishay Weiss" <[email protected]> wrote: I put the flag there just as a test. If it does what the documentation says it should it should be helpful for bigger bulks, but I haven’t gotten it to work. Yes, the total of .asc files is I think less than an mb, and yet even this hangs for me. From: Alex Harui<mailto:[email protected]> Sent: Wednesday, April 29, 2020 6:58 PM To: [email protected]<mailto:[email protected]> Subject: Re: Optimize wagon:upload Try turning off the optimize flag in the ant script where it calls Maven. If you are just uploading individual .asc files it is far less data than pushing all of the binary bits. -Alex On 4/29/20, 7:18 AM, "Yishay Weiss" <[email protected]> wrote: Has anyone got this [1] to work? Didn’t for me. I got [exec] [ERROR] Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload (default-cli) on project royale-framework-parent: Error handling resource : Wagon https does not support optimize upload -> [Help 1] [exec] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload (default-cli) on project [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Fwagon-maven-plugin%2Fupload-mojo.html%23optimize&data=02%7C01%7Caharui%40adobe.com%7C2529ad24145945bd30ea08d7ec5f7d3d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637237767178985992&sdata=p8yTTi1X7lo9fuXiDqHbBMMEK2ayhtJ3MTS79Z9Glqg%3D&reserved=0
