You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Christian Schneider <ch...@die-schneider.net> on 2014/10/24 13:14:28 UTC
Discuss Release of aries jpa bundles
The last release of aries jpa fixes an important bug but is not
compatible to jpa 2.0 providers anymore.
In the mean time we fixed this. So the current aries jpa trunk works
well with jpa 2.0 and 2.1.
I would like to release the aries bundles as soon as possible to finally
ship the fix to the bug below.
I created a feature snippet for karaf that you can use to quickly test
the current snapshots as a drop in replacement for the jpa feature.
As we currently have quite a few different versions of the jpa bundles I
would also like to sync the versions. So I propose we set all the jpa
bundles to version 1.1.0. This would then also reflect that we now
support jpa 2.1 which is not just a bugfix.
The current snapshot also includes some more improvements. For example
the EntityManager in container.context now does not use synchronized all
over the place (thanks to Guillaume) which was a severe performance
bottleneck.
Christian
-----
<feature name="jpa" description="OSGi Persistence Container"
version="1.0.4" resolver="(obr)">
<details>JPA implementation provided by Apache Aries JPA 1.0.4.
NB: this feature doesn't provide the JPA engine, you have to install one
by yourself (OpenJPA for instance)</details>
<bundle dependency="true"
start-level="30">mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1</bundle>
<bundle dependency="true"
start-level="30">mvn:org.apache.geronimo.specs/geronimo-jpa_2.0_spec/1.1</bundle>
<bundle
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.api/1.0.3-SNAPSHOT</bundle>
<bundle
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint.aries/1.0.4-SNAPSHOT</bundle>
<bundle
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.container/1.0.2-SNAPSHOT</bundle>
<bundle
start-level="30">mvn:org.apache.aries.jpa/org.apache.aries.jpa.container.context/1.0.4-SNAPSHOT</bundle>
</feature>
This is the main bug I would like to have solved in the new
https://issues.apache.org/jira/browse/ARIES-1160
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Discuss Release of aries jpa bundles
Posted by Christian Schneider <ch...@die-schneider.net>.
I am aware that it is just a one time alignment. Still I think it makes
sense to do it from time to time and then let them diverge again.
Christian
On 24.10.2014 15:26, Guillaume Nodet wrote:
> If the bundles need to be bumped, so be it.
> But if the goal of aligning is to be more obvious for users and simplify
> their usage of pa, that's wrong, because the next release may get bundles
> out of sync again, so they'd better be prepared for that. That's the main
> drawback of aligning : it makes them think they will be kept aligned, but
> that's not the case.
>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Discuss Release of aries jpa bundles
Posted by Christian Schneider <ch...@die-schneider.net>.
I was wrong with the API. Seems like all changes are already released in
jpa-api 1.0.2.
So from my side no need to bump up the versions at this time. I will
release the impl bundles using the next bugfix versions.
So I only have to release
org.apache.aries.jpa.container 1.0.1 -> 1.0.2
org.apache.aries.jpa.container.context 1.0.3 -> 1.0.4
org.apache.aries.jpa.blueprint.aries 1.0.3 -> 1.0.4
I will start to prepare the release now.
Christian
On 24.10.2014 15:26, Guillaume Nodet wrote:
> If the bundles need to be bumped, so be it.
> But if the goal of aligning is to be more obvious for users and simplify
> their usage of pa, that's wrong, because the next release may get bundles
> out of sync again, so they'd better be prepared for that. That's the main
> drawback of aligning : it makes them think they will be kept aligned, but
> that's not the case.
>
> 2014-10-24 14:49 GMT+02:00 Christian Schneider <ch...@die-schneider.net>:
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Discuss Release of aries jpa bundles
Posted by Guillaume Nodet <gn...@apache.org>.
If the bundles need to be bumped, so be it.
But if the goal of aligning is to be more obvious for users and simplify
their usage of pa, that's wrong, because the next release may get bundles
out of sync again, so they'd better be prepared for that. That's the main
drawback of aligning : it makes them think they will be kept aligned, but
that's not the case.
2014-10-24 14:49 GMT+02:00 Christian Schneider <ch...@die-schneider.net>:
> The fix for aries 1160 was indeed in the July release but the release was
> broken for usage with jpa 2.0.
>
> I do not have a strong opinion against upgrading just the bugfix versions.
> I simply think it would be more obvious for users if we sync the versions
> again.
> I do not see any adverse effects this could have. As we need to release
> all bundles anyway this seems like a good moment to do it.
>
> Btw. we introduce a new class in the API. So I think the semantic
> versioning requires that we bump up the minor version to indicate that.
>
> Christian
>
>
> On 24.10.2014 14:34, Guillaume Nodet wrote:
>
>> ARIES-1160 has been released in jpg-container 1.0.1 in july.
>> I suppose you're talking about ARIES-1251 and ARIES-1247 (though
>> ARIES-1247 is linked to ARIES-1160).
>>
>> I'm fine for a release, but we should follow the policy that was agreed on
>> and release
>> jpa-container-1.0.2
>> jpa-container-context-1.0.4
>> unless there is any incompatibilities.
>>
>> Guillaume
>>
>>
>>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>
Re: Discuss Release of aries jpa bundles
Posted by Christian Schneider <ch...@die-schneider.net>.
The fix for aries 1160 was indeed in the July release but the release
was broken for usage with jpa 2.0.
I do not have a strong opinion against upgrading just the bugfix versions.
I simply think it would be more obvious for users if we sync the
versions again.
I do not see any adverse effects this could have. As we need to release
all bundles anyway this seems like a good moment to do it.
Btw. we introduce a new class in the API. So I think the semantic
versioning requires that we bump up the minor version to indicate that.
Christian
On 24.10.2014 14:34, Guillaume Nodet wrote:
> ARIES-1160 has been released in jpg-container 1.0.1 in july.
> I suppose you're talking about ARIES-1251 and ARIES-1247 (though
> ARIES-1247 is linked to ARIES-1160).
>
> I'm fine for a release, but we should follow the policy that was agreed on
> and release
> jpa-container-1.0.2
> jpa-container-context-1.0.4
> unless there is any incompatibilities.
>
> Guillaume
>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Discuss Release of aries jpa bundles
Posted by Guillaume Nodet <gn...@apache.org>.
ARIES-1160 has been released in jpg-container 1.0.1 in july.
I suppose you're talking about ARIES-1251 and ARIES-1247 (though
ARIES-1247 is linked to ARIES-1160).
I'm fine for a release, but we should follow the policy that was agreed on
and release
jpa-container-1.0.2
jpa-container-context-1.0.4
unless there is any incompatibilities.
Guillaume
2014-10-24 13:14 GMT+02:00 Christian Schneider <ch...@die-schneider.net>:
> The last release of aries jpa fixes an important bug but is not compatible
> to jpa 2.0 providers anymore.
> In the mean time we fixed this. So the current aries jpa trunk works well
> with jpa 2.0 and 2.1.
>
> I would like to release the aries bundles as soon as possible to finally
> ship the fix to the bug below.
> I created a feature snippet for karaf that you can use to quickly test the
> current snapshots as a drop in replacement for the jpa feature.
>
> As we currently have quite a few different versions of the jpa bundles I
> would also like to sync the versions. So I propose we set all the jpa
> bundles to version 1.1.0. This would then also reflect that we now support
> jpa 2.1 which is not just a bugfix.
>
> The current snapshot also includes some more improvements. For example the
> EntityManager in container.context now does not use synchronized all over
> the place (thanks to Guillaume) which was a severe performance bottleneck.
>
> Christian
>
> -----
>
> <feature name="jpa" description="OSGi Persistence Container"
> version="1.0.4" resolver="(obr)">
> <details>JPA implementation provided by Apache Aries JPA 1.0.4.
> NB: this feature doesn't provide the JPA engine, you have to install one by
> yourself (OpenJPA for instance)</details>
> <bundle dependency="true" start-level="30">mvn:org.
> apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1</bundle>
> <bundle dependency="true" start-level="30">mvn:org.
> apache.geronimo.specs/geronimo-jpa_2.0_spec/1.1</bundle>
> <bundle start-level="30">mvn:org.apache.aries.jpa/org.apache.
> aries.jpa.api/1.0.3-SNAPSHOT</bundle>
> <bundle start-level="30">mvn:org.apache.aries.jpa/org.apache.
> aries.jpa.blueprint.aries/1.0.4-SNAPSHOT</bundle>
> <bundle start-level="30">mvn:org.apache.aries.jpa/org.apache.
> aries.jpa.container/1.0.2-SNAPSHOT</bundle>
> <bundle start-level="30">mvn:org.apache.aries.jpa/org.apache.
> aries.jpa.container.context/1.0.4-SNAPSHOT</bundle>
> </feature>
>
> This is the main bug I would like to have solved in the new
> https://issues.apache.org/jira/browse/ARIES-1160
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>