1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
## Releasing CsvJdbc
Use the following steps to create a CsvJdbc release.
* Check environment
```
java -version
```
must be 8.
* Checkout from GitHub
Push all changes from GitHub git repository to SourceForge repository
(replace `simoc` with your GitHub and SourceForge usernames).
```
git clone https://github.com/simoc/csvjdbc.git csvjdbc-github
cd csvjdbc-github
git push ssh://simoc@git.code.sf.net/p/csvjdbc/code master
```
* Checkout from SourceForge
```
git clone ssh://simoc@git.code.sf.net/p/csvjdbc/code csvjdbc-code
git clone ssh://simoc@git.code.sf.net/p/csvjdbc/website csvjdbc-website
```
* Check that XML `<property name="rel">` tag in file
`csvjdbc-code/build/build.xml` is the version number we are creating.
If not, update it and commit.
* Compile
```
cd csvjdbc-code/build
ant jar test
```
* Check that the ant test step above does not report failing unit tests
* Upload to Sourceforge web site (replace `simoc` and `1.0-29` with values
for this release).
```
sftp simoc,csvjdbc@frs.sourceforge.net
cd /home/frs/project/c/cs/csvjdbc/CsvJdbc
mkdir 1.0-29
cd 1.0-29
put target/csvjdbc-1.0-29.jar
```
* Check that XML `<project><version>` tag in file `pom.xml` is the version
number we are creating plus "-SNAPSHOT" suffix. If not, update it and
commit.
* Check that you have a `$HOME/.m2/settings.xml` file containing
the following XML tags, as described
[here](http://central.sonatype.org/pages/apache-maven.html)
and that the GPG profile contains a GPG key created using
[these steps](http://central.sonatype.org/pages/working-with-pgp-signatures.html)
```
<server><id>git.code.sf.net</id> ...
<server><id>ossrh</id> ...
<profile><id>ossrh</id> ... contains GPG profile
```
* Maven deploy to Maven Central
```
mvn release:clean release:prepare
```
(accept defaults at prompts for CsvJdbc version, git tag, next CsvJdbc
version number. You are also prompted for Sourceforge password several
times).
```
mvn release:perform
```
* Login to [Nexus Repository Manager](https://oss.sonatype.org/)
(username and password same as in `<ossrh>` XML tag in
`$HOME/.m2/settings.xml`), click on Staging Repositories in left panel,
then on row netsourceforgecsvjdbc- ..., then Close in toolbar and
Confirm in dialog box, then Release in toolbar and Confirm in dialog
box, as described
[here](http://central.sonatype.org/pages/releasing-the-deployment.html).
* Update Tracker tickets from 'Pending' to 'Closed' with a comment
that they are included in release 1.0-29.
* Create a `README.md` file listing the changed Tracker tickets and
upload to 1.0-29 directory, as in Step 7.
* Upload new `index.html` if it has changed since last release.
```
cd csvjdbc-website/www
sftp simoc@web.sourceforge.net
cd /home/project-web/c/cs/csvjdbc/htdocs
put index.html
```
|
