jsamp/hints.txt at master · mbtaylor/jsamp · GitHub

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
Notes:
------
   mvn clean
   mvn package
   mvn site
   mvn -DskipTests

On release:
-----------

(I'm pretty sure I'm comprehensively missing the point of maven by
having to do this manually).

update version number in pom.xml in TWO places:
   <project>/<version>
   <project>/<properties>/<jsampVersion>

mvn clean package site install

# 2024 I no longer have a code-signing certificate, so can't do this.
jarsigner
   -keystore /home/mbt/certs/comodo-uob.p12
   -storetype pkcs12
   -tsa http://timestamp.comodoca.com
   -signedjar target/jsamp-${pom.currentVersion}_signed.jar
   target/jsamp-${pom.currentVersion}.jar
   uob

cp target/jsamp-x.x.x.jar /home/mbt/public_html/releases/jsamp/

rm -rf /home/mbt/public_html/jsamp
mkdir /home/mbt/public_html/jsamp
cp target/jsamp-x.x.x.jar /home/mbt/public_html/jsamp/
cp -r target/site/* /home/mbt/public_html/jsamp

tag and add jar file to github release

# mvn deploy should then do the publishing to maven central.
# It used to go to OSSRSH but was forced to migrate to central in May 2025.
# Since then I've done a dry run of this, and it shows up at
# https://central.sonatype.com/publishing/deployments
# where you have to hit the publish button: see
# https://central.sonatype.org/publish/publish-portal-maven/

# It should be possible to do it manually as well, in the same way
# as for the STIL makefile.

# This uses ~/.m2/settings.xml, which looks like this, with the
# token generated from https://central.sonatype.com/account
# (see https://central.sonatype.org/publish/publish-portal-maven/)
<settings>
  <servers>
    <server>
      <id>central</id>
      <username>token-username</username>
      <password>token-password</password>
    </server>
  </servers>
</settings>