THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Follow the steps as described on http://maven.apache.org/developers/release/releasing.html (Close the staging repository)
Upload the distribution
TODO we might want to switch to https://dist.apache.org/repos/dist/dev/<TLP name>/
as explained here: http://www.apache.org/dev/release#upload-ci
Create Distribution checksums
The distribution files are now located in target/checkout/empire-db-dist
In order to create the checksums use:
| Code Block |
|---|
>cd target/checkout/empire-db-dist (we want to have the same artifacts in the dist as in the repo)
>./checksums.sh
...
All Done. Files available in ./target
|
OR (if the previous failed/is not possible any more)
this might not work, not tested, probably creates new artifacts instead of using existing ones
| Code Block |
|---|
>svn checkout https://svn.apache.org/repos/asf/empire-db/tags/apache-empire-db-2.0.5-rc3
...
>cd apache-empire-db-2.0.5-rc3/empire-db-dist/
>mvn7 clean install -Papache-release |
| Code Block |
>cd target/checkout/empire-db-dist (we want to have the same artifacts in the dist as in the repo) >./checksums.sh ... All Done. Files available in ./target |
OR (if the previous failed/is not possible any more)
this might not work, not tested, probably creates new artifacts instead of using existing ones
...
target
|
For Windows you might want to use the "File Checksum Integrity Verifier" (fciv).
...
...
...
com/en-us/download/details.aspx?id=11533
like e.g:
fciv -md5 -wp target\apache-empire-db-2.
...
4.
...
6-dist.zip > target\apache-empire-db-2.4.6-dist.zip.md5Upload the Distribution
Finally upload Now upload the generated files + rat report to your apache personal directory.
...
the distribution directory using svn.
...
...
as explained here: http://www.apache.org/dev/release#upload-ci
Now remove the .pom on the remote machine (and clean up old files)
...
Initiate a vote
Docs here: http://www.apache.org/dev/release#approving-a-release
...