Convert build to Gradle and repositories to bintray/jcenter.

[adrianbk]

@dilipkrish @fgaule @acwatson @brandon-atkinson do you guys have any work in progress. I want to pick a good time to merge the branch 'gradle-port' into master?

[dilipkrish]

👍

[fgaule]

👍

[gorjusborg]

👍

On Fri, Aug 22, 2014 at 7:37 AM, Federico Gaule notifications@github.com
wrote:

[image: 👍]

—
Reply to this email directly or view it on GitHub
#422 (comment)
.

[adrianbk]

Developer Environment

Open jdk 1.6 or JDK 1.7 (not oracle 1.6 until https://github.com/martypitt/swagger-springmvc/issues/426 issue is fixed.

You do not need to install gradle. The gradle wrapper is included in the repository.
Intellij >> File Open >> ../swagger-springmvc/build.gradle

Be sure to select 'use the default wrapper'

If asked to reuse the existing project select 'Open existing'

Publishing

We have moved away from publishing to maven central. For some reasons why read this

What about PGP signing? - read this:

There are 2 hosted systems relating to artifact publishing for this project:

1. http://oss.jfrog.org (OJO) which is the hosted repository for all snapshots, milestones, RC's and releases. OJO 's repository manager is artifactory and can be accessed via: https://oss.jfrog.org/webapp/browserepo.html
2. Bintray which is used to publish and socialise all non-snapshot releases. If you are a collaborator on this project please sign up to the swaggerspringmvc organisation https://bintray.com/swaggerspringmvc. (Click the 'join' button)

Publishing snapshots

• Set the snapshot version in ../build.gradle
  
• Run the following command from the project's root directory

./gradlew -Pbintray_username=<bintrayusername> -Pbintray_password=<bintraytoken> publish

• The artifacts should then be available in the 'oss-snapshot-local' repository. You can browse the repos from here: https://oss.jfrog.org/webapp/browserepo.html. If you need to remove snapshot artifact's login to artifactory using your bintray username and token
• NOTE SNAPSHOT's are automatically published by the CI build

Publishing releases

• Set the release, milestone or release candidate version in ../build.gradle

• Git commit & push
• Run the following command from the project's root directory

./gradlew -Pbintray_username=<bintrayusername> -Pbintray_password=<bintraytoken> publish

- This same command publishes to both OJO and bintray (for all non-snapshot releases). Similar to snapshot releases the artifacts can be seen on artifactory in the 'oss-release-local' repository

• Git tag the release
• Change he version in build.gradle to the next snapshot
• Commit and push
• Browse to the swaggerswagger mvc maven repo on bintray: https://bintray.com/swaggerspringmvc/swaggerspringmvc
• Click on publish to publish all of the latest artifacts for all of the swaggerspringmvc modules. You can also hand pick what is published by navigating into each individual module but there should be no reason to do so.

• Once you have published, click on the twitter icon to socialise the release

• Note: that after a release OJO and bintray will have linked to each other (never use the upload to bintray button!)

Artifactory Tree Browser (OJO)

[adrianbk]

@dilipkrish @fgaule @acwatson @brandon-atkinson I have pushed to master. Would be great if you guys could try it out and let me now if there are any problems or suggestions for improvement. I have bumped the version to 0.9.0-SNAPSHOT and it's been published from the CI build. All tests and the demo project functional tests have passed but I'm still a bit paranoid so it would be great to get some other eyes on this.

[gorjusborg]

First thing I noticed is that there are two readme files: README.md and readme.md.
Which is the one we intend to maintain?

[adrianbk]

@brandon-atkinson removed the duplicate readme. Got caught out by OSX case insensitive filesystem.

[canmind]

👍

[Uil-Nella]

👍