aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorJulien Eluard <[email protected]>2013-03-18 18:37:08 -0300
committerJulien Eluard <[email protected]>2013-03-18 18:37:08 -0300
commit2502cea91d05706aad16c566238639e76c8d9e4f (patch)
tree5739d3559f8dc10e996b64106513d3292686de04 /README.md
parent2483a26ddca97af5fba25550d028e90f8682d847 (diff)
Update README.md
Diffstat (limited to 'README.md')
-rwxr-xr-xREADME.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index e4efdc7..12b6c3c 100755
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
Version number changes implications are not always clearly identified. Can I be sure this new minor version didn't break the public API?
As a library writer, how to continuously validate I don't break binary compatibility?
-`semantic-versioning` is a Java library allowing to validate if library version numbers follows Semantic Versioning principles as defined by [http://semver.org](Semantic Versioning).
+`semantic-versioning` is a Java library allowing to validate (using bytecode inspection) if library version numbers follows Semantic Versioning principles as defined by [http://semver.org](Semantic Versioning).
It can check JAR files or classes to identify changes between versions and validate if the new version number is correct according to semver.
`semantic-versioning` is available as an [API](#api), a [command line tool](#cli) and a [maven enforcer](http://maven.apache.org/enforcer/maven-enforcer-plugin/) [rule](#rule).