Hi Tim,
at the moment I can not put much effort into the actual implementation
at Aries JPA. So I merely keep an overview on the issues,
help people implement what they need and work on fixes and of course do
the releases. I can work on some of the issues you mentioned
but can not promise any time frame at the moment.
Of course you or anyone else is invited to work on these issues too.
Normally I try to only assign myself to issues if I actually intend to
work on them near time.
I found that having someone assigned often discourages others from
taking the issue.
Christian
On 21.02.2017 17:21, Timothy Ward wrote:
I looked only into the issues that have fix version 2.6.0.
Surely as the project area lead you should be looking at the issues that have
affects version 2.6.0 and setting the fix version appropriately?
If you intend to implement any of these issues for 2.6.0 then please set the
fix version. This allows me to see if a release is complete feature wise.
These issues were assigned to you, as requested, when they were created as part
of preparing Aries JPA to be the reference implementation for the next version
of the OSGi Spec.
Btw. I just found that we got a big issue with Aries JPA and Karaf 4.1.0. It
seems that at least Aries JPA 2.5.0 and hibernate 5 features do not work
together as both
jpa 2.0 and 2.1 apis are installed.
This is why we need to start using the JavaJPA contract so that this sort of
thing works better!
Tim
On 21 Feb 2017, at 16:02, Christian Schneider
<[email protected]<mailto:[email protected]>> wrote:
I looked only into the issues that have fix version 2.6.0.
If you intend to implement any of these issues for 2.6.0 then please set the
fix version. This allows me to see if a release is complete feature wise.
We should only pick the low hanging fruits for this release though as at least
Giuseppe is waiting for the fix of the threading issue.
Btw. I just found that we got a big issue with Aries JPA and Karaf 4.1.0. It
seems that at least Aries JPA 2.5.0 and hibernate 5 features do not work
together as both
jpa 2.0 and 2.1 apis are installed.
Christian
On 21.02.2017 16:50, Timothy Ward wrote:
Hi Christian,
I see a lot more than one issue left, and several of them are easy to fix.
https://issues.apache.org/jira/browse/ARIES-1642
https://issues.apache.org/jira/browse/ARIES-1670
https://issues.apache.org/jira/browse/ARIES-1671
https://issues.apache.org/jira/browse/ARIES-1672
I can understand if you choose not to release a fix for 1671 until the OSGi JPA
Service 1.1 specification is final, but I think that the others should be fixed
for 2.7.
Tim
On 21 Feb 2017, at 11:19, Christian Schneider
<[email protected]<mailto:[email protected]>> wrote:
We did some bug fixes and improvements in providing the correct capapbilities.
Especially because of the threading issue found by Giuseppe I would like to do
a release quite soon.
See here for the full list of issues fixed:
https://issues.apache.org/jira/browse/ARIES/fixforversion/12338632
There is one open issue left:
https://issues.apache.org/jira/browse/ARIES-1674
but I think we can move it to 2.7.0 if I can not get a fix in until the release.
Christian
--
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
