search

blackducksoftware / ohcount4j

Line counting and language identification tool
Apache License 2.0
18 stars 8 forks source link

Put built jars on Maven Central #24

Closed khampson closed 8 years ago

khampson commented 8 years ago

Integration with Gradle/Maven etc. will be much improved if ohcount4j can be a Maven Central dependency like most other Java libraries. Currently, the user has to build it him/herself and then upload it to a local artifactory instance, or hack their build.gradle (or Maven equivalent) to grab the built jar from somewhere.

PDegenPortnoy commented 8 years ago

Would Bintray or Artifactory also be acceptable deployment targets?

PDegenPortnoy commented 8 years ago

Reference for deploying Travis CI to Bintray: https://docs.travis-ci.com/user/deployment/bintray

jgustie commented 8 years ago

I just did this for bdio, I can get it set up for Ohcount4j as well. I would suggest that we first update the group ID from commoncomp to ohcount4j, as in com.blackducksoftware.ohcount4j:ohcount4j:2.0.0-SNAPSHOT. The commoncomp made sense in BitBucket, but not here; I like the convention of using the GitHub repo ID as the group ID.

jgustie commented 8 years ago

The Bintray package is linked to JCenter, so all we need to do is publish a release to get Ohcount4j into JCenter.

We need #34 to be fixed first, but then the process for creating a release is basically:

  1. Commit and push a gradle.properties without a -SNAPSHOT version to master.
  2. Wait for the Travis build to complete.
  3. Commit and push a gradle.properties with the next -SNAPSHOT version to master.
PDegenPortnoy commented 8 years ago

34 has been fixed with #35, so we are ready to continue this process. Would the next version be "2.1.1"?

mydimension commented 8 years ago

i bumped the version to 2.1.0-SNAPSHOT

-SNAPSHOT should always precede the version it's about to be