Rename package and module, to prepare for install and deploy (#107)

* rename package and module based on kevinb9n's proposal

https://github.com/jspecify/jspecify/issues/1#issuecomment-620826847

* ci: verify gradle wrapper .jar before we use

see: https://github.com/marketplace/actions/gradle-wrapper-validation

* build: package javadoc and sources

* build: update groupId and artifactId based on discussion in #107
6 files changed
tree: 275819a6a609b7ba827c8c9f27ee8e3933fd00e3
  1. .github/
  2. docs/
  3. gradle/
  4. src/
  5. .gitattributes
  6. .gitignore
  7. AUTHORS
  8. build.gradle
  9. CONTRIBUTING.md
  10. gradle.properties
  11. gradlew
  12. gradlew.bat
  13. LICENSE
  14. README.md
README.md

jspecify

This project is a placeholder. We are using the issue tracker for some of our conversations, but the existing code in the repo does not reflect our current design decisions, and we have many decisions left to make.

An artifact of well-named and well-specified annotations to power static analysis checks.

Our focus during 2018-2021 is annotations for nullness.

This is not an officially supported product of any of the participant organizations.

How to build

Simply run ./gradlew to build artifacts. Or run ./gradlew publishToMavenLocal to install artifacts to your Local Maven Repository.