This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-servlets-resolver.git
The following commit(s) were added to refs/heads/master by this push:
new ee13640 fix link
ee13640 is described below
commit ee13640977a6ab9a986bd4c1de2a215561d9bf67
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Mon Oct 5 11:46:09 2020 +0200
fix link
---
README.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/README.md b/README.md
index eeb277c..2726a91 100644
--- a/README.md
+++ b/README.md
@@ -61,8 +61,7 @@ Short answer: exactly like you deploy your code, preferably
right next to it. Pa
4. add your scripts, using the same naming conventions that you were used to
from before [5];
5. manually define your provide and require capabilities; just kidding; add
the
[`scriptingbundle-maven-plugin`](https://github.com/apache/sling-scriptingbundle-maven-plugin)
to your build section and add its required
- properties in the `maven-bundle-plugin`'s instructions (check [these
examples](https://github.com/apache/sling-org-apache-sling-scripting
- -bundle-tracker-it/tree/master/examples/));
+ properties in the `maven-bundle-plugin`'s instructions (check [these
examples](https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker-it/tree/master/examples/));
6. `mvn clean sling:install`.
### Integration Tests
