Skip to content

Updated Redisson and HZ doco #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 7, 2021
Merged

Updated Redisson and HZ doco #130

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
190836e
Updated Redisson and HZ doco
cstamas Oct 7, 2021
016433a
Typo
cstamas Oct 7, 2021
f1633e7
Typo 2
cstamas Oct 7, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions maven-resolver-named-locks-hazelcast/src/site/markdown/index.md.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,12 +32,19 @@ Out of the box "hazelcast" (distributed) named lock implementations are the foll

${esc.hash}${esc.hash} Open Issues/Notes

- It only works when Sisu DI is used and not the bundled `AetherModule` or
`ServiceLocator` (Maven uses Sisu dependency injection).
- Usage from plugins has not been tested yet.
- The `furnace-maven-plugin` does not work this implementation because it uses `ServiceLocator` instead
of dependency injection.

${esc.hash}${esc.hash} Open Issues/Notes for Maven Resolver integrators

To use this implementation within your project, depending on how you integrate, you have following options:
- If you use Sisu DI, then all you need is to provide this module (and its dependencies) on classpath and you are done.
- If you use Guice, you need to add this module (and its dependencies) upfront, and bind them explicitly.
- If you use ServiceLocator, be aware it is deprecated, and you should move away from it. In this case, simplest is
to roll your own "bootstrap" class that does pretty much same thing as ServiceLocator was, and extend it to
instantiate these components as well.

${esc.hash}${esc.hash} Installation/Testing

- Create the directory `${maven.home}/lib/ext/hazelcast/`.
Expand Down
11 changes: 9 additions & 2 deletions maven-resolver-named-locks-redisson/src/site/markdown/index.md.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,19 @@ Out of the box "redisson" (distributed) named lock implementations are the follo

${esc.hash}${esc.hash} Open Issues/Notes

- It only works when Sisu DI is used and not the bundled `AetherModule` or
`ServiceLocator` (Maven uses Sisu dependency injection).
- Usage from plugins has not been tested yet.
- The `furnace-maven-plugin` does not work this implementation because it uses `ServiceLocator` instead
of dependency injection.

${esc.hash}${esc.hash} Open Issues/Notes for Maven Resolver integrators

To use this implementation within your project, depending on how you integrate, you have following options:
- If you use Sisu DI, then all you need is to provide this module (and its dependencies) on classpath and you are done.
- If you use Guice, you need to add this module (and its dependencies) upfront, and bind them explicitly.
- If you use ServiceLocator, be aware it is deprecated, and you should move away from it. In this case, simplest is
to roll your own "bootstrap" class that does pretty much same thing as ServiceLocator was, and extend it to
instantiate these components as well.

${esc.hash}${esc.hash} Installation/Testing

- Create the directory `${maven.home}/lib/ext/redisson/`.
Expand Down