This is what _releasesteps-upload-release-to-staging looks like <profile> <id>_releasesteps-upload-release-to-staging</id> <activation> <activeByDefault>false</activeByDefault> </activation> <modules><!-- only run on top-level, not for each module --> </modules> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>wagon-maven-plugin</artifactId> <version>2.0.0</version> <configuration> <serverId>apache.releases.https</serverId> <url>https://repository.apache.org/service/local/staging/deploy/maven2</url> </configuration> </plugin> </plugins> </build> </profile> From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Wednesday, April 29, 2020 5:08 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: wagon:upload problems
Even uploading the 534 asc files which are about 1k fails, so something is definitely weird. I think it might be repeating the upload for each project. For example, there’s only one zip.asc file, which is under artifacts\archive\target\local-release-dir\org\apache\royale\framework\royale-framework-parent\0.9.7\royale-framework-parent-0.9.7-source-release.zip.asc Yet when I run this target <target name="Test wagon" depends="get-artifact-folder" description="there’s on one zip.asc"> <fail message="release.version not specified" unless="release.version"/> <exec executable="${mvn}" dir="${artifactfolder}/sources" failonerror="true" > <arg value="wagon:upload" /> <arg value="-X" /> <arg value="-Dwagon.fromDir=${artifactfolder}/artifacts/archive/target/local-release-dir" /> <arg value="-Dwagon.includes=**/*.zip.asc" /> <arg value="-Dwagon.optimize=true" /> <arg value="-P" /> <arg value="_releasesteps-upload-release-to-staging" /> </exec> </target> I see it’s uploading it once for each project: [exec] [INFO] --- wagon-maven-plugin:2.0.0:upload (default-cli) @ Fonts --- [exec] [INFO] --- wagon-maven-plugin:2.0.0:upload (default-cli) @ Core --- [exec] [INFO] --- wagon-maven-plugin:2.0.0:upload (default-cli) @ Binding --- Etc.