Basically, it's what I proposed yeah.
I will create a Jira and do that.
Regards
JB
On 11/30/2014 11:58 PM, Christian Schneider wrote:
Not sure how the condition would work here.
How about simply having a jpa20 and a jpa21 feature including the aries
jpa bundles and the jpa respective api. Hibernate 4.3 could then refer
to the jpa21 feature and hibernate 4.2 to the jpa20 one.
Christian
Am 30.11.2014 22:36, schrieb Jean-Baptiste Onofré:
IMHO, it's a mistake in the hibernate 4.3 feature that should install
the jpa feature (by transitivity) that provide jpa 2.1 support. On the
other hand, jpa feature should install the corresponding jpa api version.
So, what I propose:
- add a jpa-api feature for both 2.0 and 2.1
- remove jpa-api bundle from the jpa feature
- add jpa-api and jpa features dependency on the engine level (with a
<condition/> or let the user uses pick the target jpa version that he
wants
WDYT ?
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
