THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Wiki Markup |
---|
When prompted for the SCM tag name, follow this pattern: {{STRUTS_2_3_\[PATCH_VERSION\]}} |
Note |
---|
For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run: |
...
After closing repository in Nexus, you must obtain the url where the assemblies are stored, it looks like belowcheck if the release files are available from staging repository as bellow:
Code Block |
---|
https://repository.apache.org/content/repositoriesgroups/orgapachestruts-300staging/org/apache/struts/struts2-assembly/$VERSION/ |
...
In order to move the assemblies login to people.apache.org and execute the following code:
Code Block | ||||
---|---|---|---|---|
| ||||
#!/bin/sh # create the destination directory mkdir $VERSION cd $VERSION # get the distro wget -erobots=off -nv -l 1 --accept=zip,md5,sha1,asc -r --no-check-certificate -nd -nH https://repository.apache.org/content/repositoriesgroups/$REPOIDstaging/org/apache/struts/struts2-assembly/$VERSION # rename files for f in *2-assembly*.zip* do mv $f `echo $f | sed s/2-assembly//g` done # remove unneeded files for f in struts2-assembly-*.pom* do rm $f done |
...