java-uitestsupport

This library ...

How to configure/use

Legal Stuff

License

Copyright 2014 Dan Haywood

Licensed under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Dependencies

This library depends on:

• junit:junit
• org.gebish:geb-core
• org.seleniumhq.selenium:selenium-support

Maven deploy notes

Only the dom module is deployed, and is done so using Sonatype's OSS support (see user guide).

Release to Sonatype's Snapshot Repo

To deploy a snapshot, use:

pushd cpt
mvn clean deploy
popd

The artifacts should be available in Sonatype's Snapshot Repo.

Release to Maven Central (scripted process)

The release.sh script automates the release process. It performs the following:

• perform sanity check (mvn clean install -o) that everything builds ok
• bump the pom.xml to a specified release version, and tag
• perform a double check (mvn clean install -o) that everything still builds ok
• release the code using mvn clean deploy
• bump the pom.xml to a specified release version

For example:

sh release.sh 1.6.1 \
              1.6.2-SNAPSHOT \
              dan@haywood-associates.co.uk \
              "this is not really my passphrase"

where

• $1 is the release version
• $2 is the snapshot version
• $3 is the email of the secret key (~/.gnupg/secring.gpg) to use for signing
• $4 is the corresponding passphrase for that secret key.

If the script completes successfully, then push changes:

git push

If the script fails to complete, then identify the cause, perform a git reset --hard to start over and fix the issue before trying again.

Release to Maven Central (manual process)

If you don't want to use release.sh, then the steps can be performed manually.

To start, call bumpver.sh to bump up to the release version, eg:

 `sh bumpver.sh 1.6.1`

which:

• edit the parent pom.xml, to change ${isis-module-command.version} to version
• edit the dom module's pom.xml version
• commit the changes
• if a SNAPSHOT, then tag

Next, do a quick sanity check:

mvn clean install -o

All being well, then release from the cpt module:

pushd cpt
mvn clean deploy -P release \
    -Dpgp.secretkey=keyring:id=dan@haywood-associates.co.uk \
    -Dpgp.passphrase="literal:this is not really my passphrase"
popd

where (for example):

• "dan@haywood-associates.co.uk" is the email of the secret key (~/.gnupg/secring.gpg) to use for signing
• the pass phrase is as specified as a literal

Other ways of specifying the key and passphrase are available, see the pgp-maven-plugin's documentation).

If (in the dom's pom.xml the nexus-staging-maven-plugin has the autoReleaseAfterClose setting set to true, then the above command will automatically stage, close and the release the repo. Sync'ing to Maven Central should happen automatically. According to Sonatype's guide, it takes about 10 minutes to sync, but up to 2 hours to update search.

If instead the autoReleaseAfterClose setting is set to false, then the repo will require manually closing and releasing either by logging onto the Sonatype's OSS staging repo or alternatively by releasing from the command line using mvn nexus-staging:release.

Finally, don't forget to update the release to next snapshot, eg:

sh bumpver.sh 1.6.2-SNAPSHOT

and then push changes.