14.6.1_2016.08.20 is released! At least that's what it says on OSS. It's
not yet showing up in maven central, but I think it might just takes a few
hours to sync.

Mark, thanks so much for sharing your build notes! They were essential to
me. I will add a few more notes for future reference:



> Preamble
> ---------
> 0) Start with a 64 bit install of Ubuntu 14.04.4
>
> 1) Install the following packages
>    sudo apt-get install mvn libsaxon-java openjdk-7-jdk ant
>
> 2) Create ~/.jmol.build.properties file with contents
>    <property name="keystore.name" value="selfSignedCertificate" />
>

3) Add your credentials to ~/.m2/settings.xml. This should include both OSS
user/password and a GPG key. Note that GPG is used to sign the full
release, in addition to the JKS self-signature configured in
~/.jmol.build.properties

<settings>
    <servers>
        <server>
            <id>sonatype-nexus-snapshots</id>
            <username>OSS_USERNAME</username>
            <password>OSS_PASSWORD</password>
        </server>
        <server>
            <id>sonatype-nexus-staging</id>
            <username>OSS_USERNAME</username>
            <password>OSS_PASSWORD</password>
        </server>
        <server>
            <id>releases</id>
            <username>OSS_USERNAME</username>
            <password>OSS_PASSWORD</password>
        </server>
    </servers>
    <profiles>
        <profile>
            <id>gpg</id>
            <properties>
                <gpg.keyname>GPG_KEY</gpg.keyname>
                <gpg.passphrase>GPG_PASSWORD</gpg.passphrase>
            </properties>
        </profile>
    </profiles>
</settings>



Main
----

1) Checkout the source from SVN or switch to the correct branch

svn checkout http://svn.code.sf.net/p/jmol/code/branches/v14_6 jmol-code
cd jmol-code/Jmol



> 2) Add a required jar to enable docs to be built
>    mv ./unused/saxon.jar ./jars/
>
> 3) Build jar target
>    ant jar
>    <input ~/.jmol.build.properties as the private property file >
>
> 4) Build dist target
>    ant dist
>    <input ~/.jmol.build.properties as the private property file >
>
>
Note that this succeeds for me with an SVN checkout.

You should now have a build/dist-maven directory with the pom and jar files.

5) Stage to OSS

   ant -f ./tools/jmol-sonatype.xml dist-release


(I assume that patch 33 <https://sourceforge.net/p/jmol/patches/33/> will
be merged in before the next release

6) Go to https://oss.sonatype.org/, find the newly staged release, and
manually 'Close' and 'Release' it. This process should be automatable, but
the 'nexus' plugin referenced in the 'close-release' and 'promote-release'
ant targets is no longer available, and I wasn't able to get its
replacement, the nexus-staging-maven-plugin
<https://books.sonatype.com/nexus-book/reference/staging-deployment.html>, to
work right.
------------------------------------------------------------------------------
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to