Skip to content

Commit 21bc32a

Browse files
pvlugterbantonsson
authored andcommitted
Use github releases for versions in readme
1 parent fbd1b8e commit 21bc32a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ Add the plugin to your `project/plugins.sbt`:
1010
addSbtPlugin("com.lightbend.sbt" % "sbt-javaagent" % versionNumber)
1111
```
1212

13-
The version number is determined by the latest package, and can be deduced from the [version.sbt](https://github.com/sbt/sbt-javaagent/blob/master/version.sbt) file, i.e. if the version.sbt is `0.1.5-SNAPSHOT` then the latest released version is probably `0.1.4`. You can see the full version packages in the bintray repository:
13+
See [sbt-javaagent releases] for a list of released versions.
1414

15-
https://dl.bintray.com/sbt/sbt-plugin-releases/com.lightbend.sbt/sbt-javaagent/scala_2.12/sbt_1.0/
15+
[sbt-javaagent releases]: https://github.com/sbt/sbt-javaagent/releases
1616

1717
## Java agent
1818

@@ -60,7 +60,7 @@ Multiple configurations can be specified. For example, the following will enable
6060
javaAgents += "com.example" % "agent" % "1.2.3" % "compile;test"
6161
```
6262

63-
Note that in this case, the agent dependency is actually added under the `provided` configuration, so that a project can compile against the agent and then have the agent provided at runtime using a `-javaagent` option.
63+
Note that in this case, the agent dependency is actually added under the `provided` configuration, so that a project can compile against the agent and then have the agent provided at runtime using a `-javaagent` option.
6464

6565
If the *compile* scope is not enabled, then the agent dependency is put under a special `javaagent` configuration so that it doesn't appear as a regular library dependency or on build classpaths.
6666

0 commit comments

Comments
 (0)