commit | e030c88a8d90da07b67ae8d99131f1caa7eb888b | [log] [tgz] |
---|---|---|
author | Raymond Augé <rotty3000@apache.org> | Mon Jul 16 20:03:27 2018 +0000 |
committer | Raymond Augé <rotty3000@apache.org> | Mon Jul 16 20:03:27 2018 +0000 |
tree | 35c5cfb50df71c9e278e6c5d4c8de4609229e714 | |
parent | f2e7b906c8de0c677a6a9350419e24ba82192bb5 [diff] |
ARIES-1814 Solve the start order limitations with SPI Fly by first creating a framework extension Signed-off-by: Raymond Auge <rotty3000@apache.org> git-svn-id: https://svn.apache.org/repos/asf/aries/trunk@1836062 13f79535-47bb-0310-9956-ffa450edef68
The Aries project consists of a set of pluggable Java components enabling an enterprise OSGi application programming model.
See Apache Aries Website.
Most of the code is still at the Aries svn repo. There is also a github mirror.
Some of the subproject are already migrated to git:
Subproject | Apache Git | Github Mirror |
---|---|---|
Aries Containers | apache | github |
Aries JAX-RS whiteboard | apache | github |
Aries JPA | apache | github |
Aries RSA | apache | github |
Aries Transaction Control | apache | github |
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.