Sounds good to me.
What do you think about also moving tx control into its own git repo?
Christian
On 14.10.2016 14:57, Timothy Ward wrote:
The OSGi Alliance has recently put out a draft release of the R7 specs,
including the Transaction Control Chapter.
There have been a lot of
The OSGi Alliance has recently put out a draft release of the R7 specs,
including the Transaction Control Chapter.
There have been a lot of improvements to the Transaction Control implementation
since the RFC was originally released. In particular there have been a lot of
fixes to the pool
We can do that but I am not sure it is really necessary.
Most of our sub projects are not very much related to each other.
In most cases you do not need other parts of aries and in the cases I
had till now I simply used them like external dependencies.
So for example when I worked on Aries RSA
The problem with documentation is... ahem... that it's often not complete :)
One thing that would be worth considering is to come up with an aries
holder git repo, that has submodule or gits or similar connections to all
the aries subcomponents. That way it would at least be possible to get
I think the most important part is to document the location of the repo
along with the module:
http://aries.apache.org/modules/rsa.html
From there it is easy to find the apache repo and the github mirror.
You are right that there is unfortunately no way to mark repos as
belonging to aries but
On the individual git repos...
I realize that this has been discussed for quite a while, but what I find
missing with that approach is an overview of the Aries projects.
All of the git repos are part of a single 'Apache' group and at least I
don't know of a way to find all the git repos that
