8:27 a.m.
Hi there,
I think we should do this again since there are some changes in master that I want to use
in metamodel, and maybe we should do this regularly to minimize the conflicts?
Steve is the best to do this, since he already did this once, but in case he is busying on
other stuff, I'm voluntarily to do this .
WDYT?
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
2:38 p.m.
Going to throw another perhaps crazy suggestion out there...
Thinking we should consider:
1) branching 4.1
2) integrating my JPA 2.1 work onto master
3) merge master (with JPA 2.1) to metamodel branch
Couple of thought processes go into this. First, I do not see us doing
anymore 4.x releases outside of possibly doing a 4.2 *specifically* to
release JPA 2.1 support. Ideally I want JPA 2.1 support to be released
as 5.0 hand-in-hand with the metamodel work. The only reason we would
not go that route is if the metamodel work drags on and threatens us
releasing JPA 2.1 support in a timely manner. I do not see that
happening, just stating a known condition. Besides the JPA 2.1 support
is actually up-to-date with the latest available specs (and actually a
little bit ahead of the latest available spec draft after this week).
So again, all-in-all I still do not foresee the need for a 4.2 at this time.
On 07/15/2012 08:27 AM, Strong Liu wrote:
Hi there,
I think we should do this again since there are some changes in master that I want to use
in metamodel, and maybe we should do this regularly to minimize the conflicts?
Steve is the best to do this, since he already did this once, but in case he is busying
on other stuff, I'm voluntarily to do this .
WDYT?
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
steve(a)hibernate.org
http://hibernate.org
10:41 p.m.
On Jul 17, 2012, at 3:38 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
Going to throw another perhaps crazy suggestion out there...
Thinking we should consider:
1) branching 4.1
2) integrating my JPA 2.1 work onto master
3) merge master (with JPA 2.1) to metamodel branch
I think this route is okay. when JPA 2.1 SPEC will be released?
Couple of thought processes go into this. First, I do not see us doing anymore 4.x
releases outside of possibly doing a 4.2 *specifically* to release JPA 2.1 support.
Ideally I want JPA 2.1 support to be released as 5.0 hand-in-hand with the metamodel work.
The only reason we would not go that route is if the metamodel work drags on and
threatens us releasing JPA 2.1 support in a timely manner. I do not see that happening,
just stating a known condition. Besides the JPA 2.1 support is actually up-to-date with
the latest available specs (and actually a little bit ahead of the latest available spec
draft after this week). So again, all-in-all I still do not foresee the need for a 4.2 at
this time.
agree, don't foresee any needs to do a 4.2 release
On 07/15/2012 08:27 AM, Strong Liu wrote:
> Hi there,
>
> I think we should do this again since there are some changes in master that I want to
use in metamodel, and maybe we should do this regularly to minimize the conflicts?
>
> Steve is the best to do this, since he already did this once, but in case he is
busying on other stuff, I'm voluntarily to do this .
>
> WDYT?
>
>
>
>
> -------------------------
> Best Regards,
>
> Strong Liu <stliu at hibernate.org>
> http://about.me/stliu/bio
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
steve(a)hibernate.org
http://hibernate.org
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
6:59 p.m.
(1) and (2) are done. Tomorrow I will work on (3).
On Tue 17 Jul 2012 03:16:46 AM CDT, Hardy Ferentschik wrote:
On Jul 16, 2012, at 9:38 PM, Steve Ebersole wrote:
> Thinking we should consider:
> 1) branching 4.1
> 2) integrating my JPA 2.1 work onto master
> 3) merge master (with JPA 2.1) to metamodel branch
+1
--
steve(a)hibernate.org
http://hibernate.org
2:19 a.m.
our CI reported some compile error :
[ant:javac] Compiling 206 source files to
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/target/classes/main
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/JoinImplementor.java:37:
types javax.persistence.criteria.Fetch<Z,X> and
javax.persistence.criteria.Join<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface JoinImplementor<Z,X> extends Join<Z,X>,
Fetch<Z,X>, FromImplementor<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/CollectionJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface CollectionJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, CollectionJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/SetJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface SetJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, SetJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/ListJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface ListJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, ListJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/MapJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,V> and
org.hibernate.jpa.criteria.JoinImplementor<Z,V> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface MapJoinImplementor<Z,K,V> extends
JoinImplementor<Z,V>, MapJoin<Z,K,V> {
[ant:javac] ^
[ant:javac] Note: Some input files use or override a deprecated API.
[ant:javac] Note: Recompile with -Xlint:deprecation for details.
[ant:javac] Note: Some input files use unchecked or unsafe operations.
[ant:javac] Note: Recompile with -Xlint:unchecked for details.
[ant:javac] 5 errors
On Jul 19, 2012, at 7:59 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
(1) and (2) are done. Tomorrow I will work on (3).
On Tue 17 Jul 2012 03:16:46 AM CDT, Hardy Ferentschik wrote:
>
> On Jul 16, 2012, at 9:38 PM, Steve Ebersole wrote:
>
>> Thinking we should consider:
>> 1) branching 4.1
>> 2) integrating my JPA 2.1 work onto master
>> 3) merge master (with JPA 2.1) to metamodel branch
>
> +1
>
--
steve(a)hibernate.org
http://hibernate.org
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
6:48 a.m.
This is the deal discussed earlier on the dev list about jdk 1.6 javac
bug. For now we will need to use jdk 1.7
On Jul 19, 2012 2:20 AM, "Strong Liu" <stliu(a)hibernate.org> wrote:
our CI reported some compile error :
[ant:javac] Compiling 206 source files to
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/target/classes/main
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/JoinImplementor.java:37:
types javax.persistence.criteria.Fetch<Z,X> and
javax.persistence.criteria.Join<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface JoinImplementor<Z,X> extends Join<Z,X>,
Fetch<Z,X>, FromImplementor<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/CollectionJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface CollectionJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, CollectionJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/SetJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface SetJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, SetJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/ListJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,X> and
org.hibernate.jpa.criteria.JoinImplementor<Z,X> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface ListJoinImplementor<Z,X> extends
JoinImplementor<Z,X>, ListJoin<Z,X> {
[ant:javac] ^
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/jpa/criteria/MapJoinImplementor.java:35:
types org.hibernate.jpa.criteria.JoinImplementor<Z,V> and
org.hibernate.jpa.criteria.JoinImplementor<Z,V> are incompatible; both define
on(javax.persistence.criteria.Predicate[]), but with unrelated return types
[ant:javac] public interface MapJoinImplementor<Z,K,V> extends
JoinImplementor<Z,V>, MapJoin<Z,K,V> {
[ant:javac] ^
[ant:javac] Note: Some input files use or override a deprecated API.
[ant:javac] Note: Recompile with -Xlint:deprecation for details.
[ant:javac] Note: Some input files use unchecked or unsafe operations.
[ant:javac] Note: Recompile with -Xlint:unchecked for details.
[ant:javac] 5 errors
On Jul 19, 2012, at 7:59 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
(1) and (2) are done. Tomorrow I will work on (3).
On Tue 17 Jul 2012 03:16:46 AM CDT, Hardy Ferentschik wrote:
On Jul 16, 2012, at 9:38 PM, Steve Ebersole wrote:
Thinking we should consider:
1) branching 4.1
2) integrating my JPA 2.1 work onto master
3) merge master (with JPA 2.1) to metamodel branch
+1
--
steve(a)hibernate.org
http://hibernate.org
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
4559
days inactive
4563
days old
6 comments
3 participants
participants (3)
-
Hardy Ferentschik -
Steve Ebersole -
Strong Liu