Bump org.mockito:mockito-core from 4.9.0 to 5.9.0 in /spi-fly

Bumps [org.mockito:mockito-core](https://github.com/mockito/mockito) from 4.9.0 to 5.9.0.
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](https://github.com/mockito/mockito/compare/v4.9.0...v5.9.0)

---
updated-dependencies:
- dependency-name: org.mockito:mockito-core
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: 70e34411f721d1a82b0a0f42120ddcd9729c857f
  1. .github/
  2. application/
  3. async/
  4. blueprint/
  5. eba-maven-plugin/
  6. ejb/
  7. esa-ant-task/
  8. esa-maven-plugin/
  9. jmx/
  10. jndi/
  11. jpa/
  12. parent/
  13. proxy/
  14. pushstream/
  15. quiesce/
  16. samples/
  17. sandbox/
  18. spi-fly/
  19. subsystem/
  20. testsupport/
  21. transaction/
  22. tutorials/
  23. tx-control/
  24. util/
  25. versioning/
  26. web/
  27. .gitignore
  28. .mailmap
  29. LICENSE
  30. NOTICE
  31. pom.xml
  32. README.md
README.md

Apache Aries

The Aries project consists of a set of pluggable Java components enabling an enterprise OSGi application programming model.

See Apache Aries Website.

SPI Fly - CI Build

Source Code

The sources are now directly availble in aries github.

Some of the subprojects have their own git repos:

Subproject
Aries CDI
Aries Component DSL
Aries Containers
Aries JAX-RS whiteboard
Aries JPA
Aries RSA
Aries Transaction Control

Build

Most projects can be built using

mvn clean install

As the Aries svn hosts a lot of different subprojects it makes sense to only build the specific subproject.