/spring-ws

Spring Web Services

Primary LanguageJava

Spring Web Services

CircleCI

Spring Web Services is a product of the Spring community focused on creating document-driven Web services. Spring Web Services aims to facilitate contract-first SOAP service development, allowing for the creation of flexible web services using one of the many ways to manipulate XML payloads.

Installation

Releases of Spring Web Services are available for download from Maven Central, as well as our own repository, http://repo.springsource.org/release.

Please visit https://projects.spring.io/spring-ws to get the right Maven/Gradle settings for your selected version.

Building Spring Web Services

  1. Run mvn clean package

This will generate the artifacts.

You can also import the project into your IDE.

Releasing Spring Web Services

Snapshots are published automatically via CI server by doing this:

$ USERNAME=<username> PASSWORD=<encrypted password> ./mvnw -Pdistribute,snapshot,docs clean -Dmaven.test.skip=true deploy
Important
 Snapshots do NOT include GPG signatures. To do so would require putting a private key on the CI server. The process for releases (below) is manual and DOES include GPG signatures.

To do a release (.RELEASE, .RC?, .M?):

  1. Check in all changes and ensure there are no edited files.

  2. Bump up the version in ALL pom.xml files to the desired version (e.g. mvn versions:set -DnewVersion=3.0.0.RC1) and commit the change.

  3. git tag <version> (like v3.0.0.RC1)

  4. Execute a maven test (./mvnw -Pdistribute,snapshot,docs clean test).

  5. Execute a maven deploy.

    • For a milestone: USERNAME=<user> PASSWORD=<encrypted password> ./mvnw -Pdistribute,milestone,docs clean -Dmaven.test.skip=true deploy

    • For a release: USERNAME=<user> PASSWORD=<encrypted password> ./mvnw -Pdistribute,release,docs clean -Dmaven.test.skip=true deploy

    • For a release to maven central: USERNAME=<user> PASSWORD=<nexus password> ./mvnw -Pdistribute,gpg,central,docs clean -Dmaven.test.skip=true deploy -s settings.xml

  6. Bump up the version in ALL pom.xml files again to the next BUILD-SNAPSHOT.

  7. Commit the change.

  8. git push (This will push the tagged version along with the release AND the new snapshot commit)

  9. Inspect handiwork at https://repo.spring.io/ or https://oss.sonatype.org/#stagingRepositories

Note
 A word about reference documentation. Based upon this, the distribute profile contains an artifactory property that is applied to the ZIP file generated by the docs profile. A CRON job will scoop up the zipped up docs and unpack them inside the target location.

Code of Conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.

Spring Web Services Project Site

You can find the documentation, issue management, support, samples, and guides for using Spring Web Services at http://projects.spring.io/spring-ws/

Documentation

See the current Javadoc and reference docs.

Issue Tracking

Spring Web Services uses JIRA for issue tracking purposes

License

Spring Web Services is Apache 2.0 licensed.