Re: Aries Transaction Control 0.0.2

2016-10-14 Thread Christian Schneider 

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 I never had to look into any 
other Aries project.


Christian

On 14.10.2016 17:21, David Bosschaert wrote:

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
everything with a single command...

I think other Apache projects are thinking about something similar. At
least the Sling community is planning to do something like this [1].

Cheers,

David

[1]
https://lists.apache.org/thread.html/37765304556b17a04e7eb122afd895ea7beae957d56c9d4501a9f2e0@%3Cdev.sling.apache.org%3E

On 14 October 2016 at 15:52, Christian Schneider 
wrote:


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 I think prepending the name with aries already help
a bit.

Actually I don't think the separate repos are a big problem for users or
developers who want to help out.
As long as we document well how to participate it might even be easier for
new devs as each repo is small and cohesive.
You check it out, do mvn clean install at the top and are done.

Of course it is difficult for current Aries committers and PMCs to keep an
overview over all changes but that was always difficult in Aries. Aries is
a collection of quite diverse projects.

Christian


On 14.10.2016 16:29, Timothy Ward wrote:


I would love to start using Git, but I agree with David that it’s
important not to lose the link with Aries, transaction control could easily
get lost without it. In some ways the Aries RSA code already suffers from
this - you can’t easily find the code from the Aries website or see it the
documentation on the website.




On 14 Oct 2016, at 14:58, David Bosschaert 

wrote:

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 belong to Aries.

In github they use organisations to provide such groupings, but since
ours
all show up under 'Apache' this doesn't help here.

With SVN you at least get all the Aries-related projects in one folder,
well at least you used to before the separate git repos appeared. Is
there
any way to get such a view back with the git approach?

Cheers,

David

On 14 October 2016 at 15:13, Christian Schneider <
ch...@die-schneider.net>
wrote:

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 improvements to the Transaction Control
implementation since the RFC was originally released.  In particular
there
have been a lot of fixes to the pool lifecycle management, and the XA
JDBC
resource provider now implements the recovery portion of the
specification

I therefore propose a 0.0.2 release of the Aries Transaction Control
code
including these improvements. I’m not aware of any outstanding bugs,
so I
propose to start work on the release immediately.

Thanks,

Tim



--

Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com




--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: Aries Transaction Control 0.0.2

2016-10-14 Thread David Bosschaert 
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
everything with a single command...

I think other Apache projects are thinking about something similar. At
least the Sling community is planning to do something like this [1].

Cheers,

David

[1]
https://lists.apache.org/thread.html/37765304556b17a04e7eb122afd895ea7beae957d56c9d4501a9f2e0@%3Cdev.sling.apache.org%3E

On 14 October 2016 at 15:52, Christian Schneider 
wrote:

> 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 I think prepending the name with aries already help
> a bit.
>
> Actually I don't think the separate repos are a big problem for users or
> developers who want to help out.
> As long as we document well how to participate it might even be easier for
> new devs as each repo is small and cohesive.
> You check it out, do mvn clean install at the top and are done.
>
> Of course it is difficult for current Aries committers and PMCs to keep an
> overview over all changes but that was always difficult in Aries. Aries is
> a collection of quite diverse projects.
>
> Christian
>
>
> On 14.10.2016 16:29, Timothy Ward wrote:
>
>> I would love to start using Git, but I agree with David that it’s
>> important not to lose the link with Aries, transaction control could easily
>> get lost without it. In some ways the Aries RSA code already suffers from
>> this - you can’t easily find the code from the Aries website or see it the
>> documentation on the website.
>>
>>
>>
>>
>> On 14 Oct 2016, at 14:58, David Bosschaert 
>>> wrote:
>>>
>>> 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 belong to Aries.
>>>
>>> In github they use organisations to provide such groupings, but since
>>> ours
>>> all show up under 'Apache' this doesn't help here.
>>>
>>> With SVN you at least get all the Aries-related projects in one folder,
>>> well at least you used to before the separate git repos appeared. Is
>>> there
>>> any way to get such a view back with the git approach?
>>>
>>> Cheers,
>>>
>>> David
>>>
>>> On 14 October 2016 at 15:13, Christian Schneider <
>>> ch...@die-schneider.net>
>>> wrote:
>>>
>>> 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 improvements to the Transaction Control
> implementation since the RFC was originally released.  In particular
> there
> have been a lot of fixes to the pool lifecycle management, and the XA
> JDBC
> resource provider now implements the recovery portion of the
> specification
>
> I therefore propose a 0.0.2 release of the Aries Transaction Control
> code
> including these improvements. I’m not aware of any outstanding bugs,
> so I
> propose to start work on the release immediately.
>
> Thanks,
>
> Tim
>
>
>
> --
 Christian Schneider
 http://www.liquid-reality.de

 Open Source Architect
 http://www.talend.com



>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>

Re: Aries Transaction Control 0.0.2

2016-10-14 Thread Christian Schneider 
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 I think prepending the name with aries already 
help a bit.


Actually I don't think the separate repos are a big problem for users or 
developers who want to help out.
As long as we document well how to participate it might even be easier 
for new devs as each repo is small and cohesive.

You check it out, do mvn clean install at the top and are done.

Of course it is difficult for current Aries committers and PMCs to keep 
an overview over all changes but that was always difficult in Aries. 
Aries is a collection of quite diverse projects.


Christian

On 14.10.2016 16:29, Timothy Ward wrote:

I would love to start using Git, but I agree with David that it’s important not 
to lose the link with Aries, transaction control could easily get lost without 
it. In some ways the Aries RSA code already suffers from this - you can’t 
easily find the code from the Aries website or see it the documentation on the 
website.





On 14 Oct 2016, at 14:58, David Bosschaert  wrote:

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 belong to Aries.

In github they use organisations to provide such groupings, but since ours
all show up under 'Apache' this doesn't help here.

With SVN you at least get all the Aries-related projects in one folder,
well at least you used to before the separate git repos appeared. Is there
any way to get such a view back with the git approach?

Cheers,

David

On 14 October 2016 at 15:13, Christian Schneider 
wrote:


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 improvements to the Transaction Control
implementation since the RFC was originally released.  In particular there
have been a lot of fixes to the pool lifecycle management, and the XA JDBC
resource provider now implements the recovery portion of the specification

I therefore propose a 0.0.2 release of the Aries Transaction Control code
including these improvements. I’m not aware of any outstanding bugs, so I
propose to start work on the release immediately.

Thanks,

Tim




--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: Aries Transaction Control 0.0.2

2016-10-14 Thread David Bosschaert 
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 belong to Aries.

In github they use organisations to provide such groupings, but since ours
all show up under 'Apache' this doesn't help here.

With SVN you at least get all the Aries-related projects in one folder,
well at least you used to before the separate git repos appeared. Is there
any way to get such a view back with the git approach?

Cheers,

David

On 14 October 2016 at 15:13, Christian Schneider 
wrote:

> 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 improvements to the Transaction Control
>> implementation since the RFC was originally released.  In particular there
>> have been a lot of fixes to the pool lifecycle management, and the XA JDBC
>> resource provider now implements the recovery portion of the specification
>>
>> I therefore propose a 0.0.2 release of the Aries Transaction Control code
>> including these improvements. I’m not aware of any outstanding bugs, so I
>> propose to start work on the release immediately.
>>
>> Thanks,
>>
>> Tim
>>
>>
>>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>

Re: Aries Transaction Control 0.0.2

2016-10-14 Thread Christian Schneider 

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 improvements to the Transaction Control implementation 
since the RFC was originally released.  In particular there have been a lot of 
fixes to the pool lifecycle management, and the XA JDBC resource provider now 
implements the recovery portion of the specification

I therefore propose a 0.0.2 release of the Aries Transaction Control code 
including these improvements. I’m not aware of any outstanding bugs, so I 
propose to start work on the release immediately.

Thanks,

Tim





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Aries Transaction Control 0.0.2

2016-10-14 Thread Timothy Ward 
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 lifecycle management, and the XA JDBC resource provider now 
implements the recovery portion of the specification

I therefore propose a 0.0.2 release of the Aries Transaction Control code 
including these improvements. I’m not aware of any outstanding bugs, so I 
propose to start work on the release immediately.

Thanks,

Tim