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.apac
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 user
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 t
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 t
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
+1 for a release
RegardsÂ
JB
Sent from my Samsung Galaxy smartphone.
Original message
From: Christian Schneider
Date:24/10/2014 13:14 (GMT+01:00)
To: dev@aries.apache.org
Cc:
Subject: Discuss Release of aries jpa bundles
The last release of aries jpa fixes an
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
