[hibernate-dev] IntelliJ 16 and Java 8 for tests
We have been having an ongoing discussion about using Java 8 features in tests. My only argument against that was the fact that doing so makes it impossible to run tests in IDE (IntelliJ at least) unless I set the "language level" for the whole module to Java 8 which means I possibly miss using Java 8 calls in src/main. Well IntelliJ 16 is in EAP and I have been using it for almost a week now. One of its major changes is a move to a more Gradle-like view of a module on importing a Gradle project. So when I import ORM, hibernate-core e.g. is split up into 2 IntelliJ modules... or more correctly one per SourceSet. Now I can set the "language level" independently of main versus test. So once IntelliJ 16 becomes more stable, I think we can consider allowing Java 8 features in tests if anyone still wants to. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate ORM FAQ in JBoss wiki
Vlad, all, In the JBoss.org wiki there are several interesting FAQs around Hibernate ORM: https://developer.jboss.org/en/hibernate/faq They provide very useful info (just learned something new by reading them), but since the last updated more than five years have passed. So I suppose some stuff is outdated by now. Assuming those contents are worth keeping, it would be great if they could be revised, sorted out / updated as needed and moved over to http://hibernate.org/orm/faq/ eventually. Do you think you could take a look at these at some point? I know it's fair bit of work, but the Hibernate community would be deeply grateful to your forever :) Cheers, --Gunnar ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate ORM FAQ in JBoss wiki
Thanks for the hint. I didn't even know about their existence. I added it to my TODO list. Vlad On Tue, Feb 16, 2016 at 5:24 PM, Gunnar Morling wrote: > Vlad, all, > > In the JBoss.org wiki there are several interesting FAQs around Hibernate > ORM: > > https://developer.jboss.org/en/hibernate/faq > > They provide very useful info (just learned something new by reading > them), but since the last updated more than five years have passed. So > I suppose some stuff is outdated by now. > > Assuming those contents are worth keeping, it would be great if they > could be revised, sorted out / updated as needed and moved over to > http://hibernate.org/orm/faq/ eventually. > > Do you think you could take a look at these at some point? I know it's > fair bit of work, but the Hibernate community would be deeply grateful > to your forever :) > > Cheers, > > --Gunnar > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] HHH-10500 and multiple associations using the same foreign key column
There is a case about association shared in a inheritance case that I don't
fully recollect. I was against supporting as it did break OO when you thought
about it - at least when I thought about it.
But this case seems to be different. Does someone explicitly asks for that use
case ?
> On 13 févr. 2016, at 22:56, Gail Badner wrote:
>
> For joined inheritance, such as:
>
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @Table(name = "task_base")
> public class TaskBase { ... }
>
> @Entity
> @Table(name = "task")
> public class Task extends TaskBase { ... }
>
> Does JPA allow mapping a one-to-many association with the foreign key
> column in a superclass table (task_base)? For example:
>
> @Entity
> public class Goal {
>...
>@OneToMany(targetEntity = TaskBase.class)
>@JoinColumn(name = "goal_id", table = "task_base")
>private Set tasks = new HashSet();
>...
> }
>
> Currently, Hibernate throws: org.hibernate.cfg.NotYetImplementedException:
> Collections having FK in secondary table.
>
> As you can see. the foreign key is actually in the superclass table.
>
> JPA 2.1 spec says this for the description of @JoinColumn( name="..." )
> when used for a unidirectional one-to-many association:
>
> "If the join is for a unidirectional OneToMany mapping using a foreign key
> mapping strategy, the foreign key is in the table of the target entity."
>
> Is "the table of the target entity" just a default that can be overridden
> by the "table" attribute? If so, then this is a bug in Hibernate.
>
> Another question, does JPA allow multiple associations to use the same
> foreign key column? For example:
>
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @Table(name = "task_base")
> public class TaskBase { ... }
>
> @Entity
> @Table(name = "task")
> public class Task extends TaskBase { ... }
>
> @Entity
> @Table(name = "othertask")
> public class OtherTask extends TaskBase { ... }
>
> @Entity
> public class Goal {
>...
>@OneToMany
>@JoinColumn(name = "goal_id", table = "task_base")
>private Set tasks = new HashSet();
>
>@OneToMany
>@JoinColumn(name = "goal_id", table = "task_base")
>private Set otherTasks = new HashSet();
>...
> }
>
> The above also fails with NotYetImplementedException for the same reason.
>
> I've created a pull request with this test case. [1]
>
> When I switched to use single table inheritance, there was no failure, but
> when Goal.tasks is loaded, it contained both Task and OtherTask objects.
>
> Is this an invalid use case or a Hibernate bug?
>
> Thanks,
> Gail
>
> [1] https://github.com/hibernate/hibernate-orm/pull/1265
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Who deleted http://docs.jboss.org/hibernate/validator ?
+1. I like the idea to land on current by default and be able to go to older versions of the documentation section if requested. It will require some work but I do think that it is doable in Awestruct. Maybe Vlad could spend some time mocking a website in that configuration and once we converge start working in the Awestruct implementation. I would rather see Vlad working on it as he is our doc focused expert. Davide and I can offer Awestruct assistance of course. > On 12 févr. 2016, at 19:12, Steve Ebersole wrote: > > Emmanuel, Davide, etal... > > I think I want to redo that decision to put versioned links on the nav. > That was always just a temp solution, as it was the easiest way to add > handling for versioned docs. But as I add 5.1 docs we would now have 4 > links on the nav for docs. That's starting to get fugly. > > Instead I'd like to have one link (Documentation) that points to a page for > "current" documentation. Then from that page (and all the versioned doc > pages) I'd like to have a set of links to older docs (or docs by version). > Ideas on how to best achieve that in our website build? > > >> On Fri, Feb 12, 2016 at 12:05 PM Steve Ebersole wrote: >> >> Vlad, today I will work updating the website for ORM. Versioned >> information (documentation) is very difficult to deal with there (imho) >> >> On Fri, Feb 12, 2016 at 12:01 PM Steve Ebersole >> wrote: >> >>> I went all the way back to 3.0. rsync started >>> >>> On Fri, Feb 12, 2016 at 11:44 AM Gunnar Morling >>> wrote: >>> The more, the better. At least 4.3 is needed as it's the last BV 1.0 compatible version. I don't exactly remember what we had there, but I suppose all the way back till 3.0. So if you are at 4.2, you are almost there :) 2016-02-12 18:31 GMT+01:00 Steve Ebersole : > so far I have downloaded back to 4.2. Should I stop at 5.0? > > > On Fri, Feb 12, 2016 at 11:25 AM Gunnar Morling > wrote: >> >> Hey, >> >> That's weird indeed. Last time I checked (at the time of the HV 5.2.3 >> release), everything was still in place. >> >> http://hibernate.org/validator/documentation/ links to the following: >> >> * http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html/ >> * http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/ >> * http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/pdf/hibernate_validator_reference.pdf >> * http://docs.jboss.org/hibernate/validator/5.3/api/ (JavaDoc) >> >> And the same for 5.2 and 4.3. Would be great to restore these ones and >> the "stable" alias at least; 5.1 and 5.0 would be bonus I suppose. >> >> Thanks, Steve, if you are taking this over. >> >> --Gunnar >> >> >> >> >> >> >> >> 2016-02-12 18:16 GMT+01:00 Davide D'Alto : >>> Links seems to be in the format x.y >>> At least looking at the links on >>> http://hibernate.org/validator/documentation/ >>> >>> >>> >>> On Fri, Feb 12, 2016 at 5:08 PM, Steve Ebersole < st...@hibernate.org> >>> wrote: >>> What's the level of versions for the validator docs on the server? x.y? On Fri, Feb 12, 2016 at 10:59 AM Steve Ebersole < st...@hibernate.org> wrote: > If the old style guides were there after the release, but gone since > I > uploaded yesterday then maybe my upload also affected the validator > docs. > No idea how that could have happened though. > > Anyway, I checked an the validator release bundles do in fact contain > the > docs. I can work on restoring those. > > Sorry (if that really was me). > > On Fri, Feb 12, 2016 at 10:53 AM Steve Ebersole < st...@hibernate.org> > wrote: > >> But thats a completely different URL Vlad. That is a UR to the >> hibernate.org server. Not the doc server. >> >> On Fri, Feb 12, 2016 at 10:48 AM Vlad Mihalcea >> >> wrote: >> >>> The 5.1 docs are also missing too: >>> >>> http://hibernate.org/orm/documentation/5.1 >>> >>> I remember I saw the old-style guide right after the 5.1 release. >>> >>> Vlad >>> >>> On Fri, Feb 12, 2016 at 6:44 PM, Steve Ebersole >>> >>> wrote: >>> That's strange. As far as I know we actually cannot delete from there. At least I was not allowed to delete from orm/5.1 yesterday when I was doing work. As for restoring, I do not know if backups are kept. We could open a ticket and see. If
Re: [hibernate-dev] How best to eliminate the Javassist dependency from Hibernate applications...
https://hibernate.atlassian.net/browse/HHH-10536 is for tracking this. Please revise as it makes sense. In the related WildFly dev discussion about $subject, Stuart asked if we would have two separate Hibernate ORM jars (one that depends on the shaded Javassist and one that depends on regular Javassist). That seems like a separate concern but perhaps others will feel stronger about it. Also, in the WildFly discussion, I asked whether it makes a difference to Hibernate, whether the javassist.util.proxy classes that we want to shade, are in the javassist.jar or a new javassist-runtime.jar? If we shade all of the classes in a javassist-runtime.jar, that might be a better long term contract, then if we shaded the javassist.util.proxy classes which could be renamed over time. Does it make a difference whether we shade the javassist.util.proxy or entire javassist-runtime.jar? Thanks, Scott ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] HHH-10500 and multiple associations using the same foreign key column
Someone has been doing the following so that multiple associations with
entities within a joined inheritance hierarchy share the same foreign key:
1) each association that shares the same foreign key uses @OneToMany(
targetEntity= ) so that the FK is in the superclass;
2) each association uses a filter to only include entities with a
particular discriminator value.
The SQL for loading each of these associations involves an outer join to
each subclass table, then the filter restricts to the particular entity
class of interest for the particular association.
I'm trying to figure out if there is a JPA-supported way that would not
involving outer joining all the subclass tables (e.g., using the
parameterized type of the collection as default for targetEntity along with
@JoinColumn(table="superclass_table") ).
Thanks,
Gail
On Tue, Feb 16, 2016 at 10:48 AM, Emmanuel Bernard
wrote:
> There is a case about association shared in a inheritance case that I
> don't fully recollect. I was against supporting as it did break OO when
> you thought about it - at least when I thought about it.
> But this case seems to be different. Does someone explicitly asks for that
> use case ?
>
> > On 13 févr. 2016, at 22:56, Gail Badner wrote:
> >
> > For joined inheritance, such as:
> >
> > @Entity
> > @Inheritance(strategy = InheritanceType.JOINED)
> > @Table(name = "task_base")
> > public class TaskBase { ... }
> >
> > @Entity
> > @Table(name = "task")
> > public class Task extends TaskBase { ... }
> >
> > Does JPA allow mapping a one-to-many association with the foreign key
> > column in a superclass table (task_base)? For example:
> >
> > @Entity
> > public class Goal {
> >...
> >@OneToMany(targetEntity = TaskBase.class)
> >@JoinColumn(name = "goal_id", table = "task_base")
> >private Set tasks = new HashSet();
> >...
> > }
> >
> > Currently, Hibernate throws:
> org.hibernate.cfg.NotYetImplementedException:
> > Collections having FK in secondary table.
> >
> > As you can see. the foreign key is actually in the superclass table.
> >
> > JPA 2.1 spec says this for the description of @JoinColumn( name="..." )
> > when used for a unidirectional one-to-many association:
> >
> > "If the join is for a unidirectional OneToMany mapping using a foreign
> key
> > mapping strategy, the foreign key is in the table of the target entity."
> >
> > Is "the table of the target entity" just a default that can be overridden
> > by the "table" attribute? If so, then this is a bug in Hibernate.
> >
> > Another question, does JPA allow multiple associations to use the same
> > foreign key column? For example:
> >
> > @Entity
> > @Inheritance(strategy = InheritanceType.JOINED)
> > @Table(name = "task_base")
> > public class TaskBase { ... }
> >
> > @Entity
> > @Table(name = "task")
> > public class Task extends TaskBase { ... }
> >
> > @Entity
> > @Table(name = "othertask")
> > public class OtherTask extends TaskBase { ... }
> >
> > @Entity
> > public class Goal {
> >...
> >@OneToMany
> >@JoinColumn(name = "goal_id", table = "task_base")
> >private Set tasks = new HashSet();
> >
> >@OneToMany
> >@JoinColumn(name = "goal_id", table = "task_base")
> >private Set otherTasks = new HashSet();
> >...
> > }
> >
> > The above also fails with NotYetImplementedException for the same reason.
> >
> > I've created a pull request with this test case. [1]
> >
> > When I switched to use single table inheritance, there was no failure,
> but
> > when Goal.tasks is loaded, it contained both Task and OtherTask objects.
> >
> > Is this an invalid use case or a Hibernate bug?
> >
> > Thanks,
> > Gail
> >
> > [1] https://github.com/hibernate/hibernate-orm/pull/1265
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Who deleted http://docs.jboss.org/hibernate/validator ?
Hi, I can surely take a look on this. We just need to discuss which task has higher priority: this one or finishing the User Guide. Since we have a single HTML doc, we could, at first, have an upper toolbar with all currently supported doc versions: 5.1, 5.0, 4.3, 4.2 By default, we load current which is the latest version. When the user clicks 4.2, we just go to http://docs.jboss.org/hibernate/orm/4.2/manual/en-US/html_single/ If he clicks 5.0, we go to http://docs.jboss.org/hibernate/orm/5.0/manual/en-US/html_single/ If he clicks 5.1, he navigates to http://docs.jboss.org/hibernate/orm/5.1/userguide/html_single/Hibernate_User_Guide.html Is this what you were thinking of too? Vlad On Tue, Feb 16, 2016 at 8:54 PM, Emmanuel Bernard wrote: > +1. I like the idea to land on current by default and be able to go to > older versions of the documentation section if requested. > > It will require some work but I do think that it is doable in Awestruct. > > Maybe Vlad could spend some time mocking a website in that configuration > and once we converge start working in the Awestruct implementation. > I would rather see Vlad working on it as he is our doc focused expert. > Davide and I can offer Awestruct assistance of course. > > > On 12 févr. 2016, at 19:12, Steve Ebersole wrote: > > > > Emmanuel, Davide, etal... > > > > I think I want to redo that decision to put versioned links on the nav. > > That was always just a temp solution, as it was the easiest way to add > > handling for versioned docs. But as I add 5.1 docs we would now have 4 > > links on the nav for docs. That's starting to get fugly. > > > > Instead I'd like to have one link (Documentation) that points to a page > for > > "current" documentation. Then from that page (and all the versioned doc > > pages) I'd like to have a set of links to older docs (or docs by > version). > > Ideas on how to best achieve that in our website build? > > > > > >> On Fri, Feb 12, 2016 at 12:05 PM Steve Ebersole > wrote: > >> > >> Vlad, today I will work updating the website for ORM. Versioned > >> information (documentation) is very difficult to deal with there (imho) > >> > >> On Fri, Feb 12, 2016 at 12:01 PM Steve Ebersole > >> wrote: > >> > >>> I went all the way back to 3.0. rsync started > >>> > >>> On Fri, Feb 12, 2016 at 11:44 AM Gunnar Morling > >>> wrote: > >>> > The more, the better. At least 4.3 is needed as it's the last BV 1.0 > compatible version. I don't exactly remember what we had there, but I > suppose all the way back till 3.0. So if you are at 4.2, you are > almost there :) > > 2016-02-12 18:31 GMT+01:00 Steve Ebersole : > > so far I have downloaded back to 4.2. Should I stop at 5.0? > > > > > > On Fri, Feb 12, 2016 at 11:25 AM Gunnar Morling < > gun...@hibernate.org> > > wrote: > >> > >> Hey, > >> > >> That's weird indeed. Last time I checked (at the time of the HV > 5.2.3 > >> release), everything was still in place. > >> > >> http://hibernate.org/validator/documentation/ links to the > following: > >> > >> * > http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html/ > >> * > > http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/ > >> * > > http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/pdf/hibernate_validator_reference.pdf > >> * http://docs.jboss.org/hibernate/validator/5.3/api/ (JavaDoc) > >> > >> And the same for 5.2 and 4.3. Would be great to restore these ones > and > >> the "stable" alias at least; 5.1 and 5.0 would be bonus I suppose. > >> > >> Thanks, Steve, if you are taking this over. > >> > >> --Gunnar > >> > >> > >> > >> > >> > >> > >> > >> 2016-02-12 18:16 GMT+01:00 Davide D'Alto : > >>> Links seems to be in the format x.y > >>> At least looking at the links on > >>> http://hibernate.org/validator/documentation/ > >>> > >>> > >>> > >>> On Fri, Feb 12, 2016 at 5:08 PM, Steve Ebersole < > st...@hibernate.org> > >>> wrote: > >>> > What's the level of versions for the validator docs on the server? > x.y? > > On Fri, Feb 12, 2016 at 10:59 AM Steve Ebersole < > st...@hibernate.org> > wrote: > > > If the old style guides were there after the release, but gone > since > > I > > uploaded yesterday then maybe my upload also affected the > validator > > docs. > > No idea how that could have happened though. > > > > Anyway, I checked an the validator release bundles do in fact > contain > > the > > docs. I can work on restoring those. > > > > Sorry (if that really was me). > > > > On Fri, Feb 12, 2016 at 10:53 AM Steve Ebersole < > st...@hibernate.org> > > wrote: > > > >> Bu
Re: [hibernate-dev] Who deleted http://docs.jboss.org/hibernate/validator ?
No, personally I am talking strictly about the hibernate.org/orm/documentation nav On Tue, Feb 16, 2016 at 3:14 PM Vlad Mihalcea wrote: > Hi, > > I can surely take a look on this. We just need to discuss which task has > higher priority: this one or finishing the User Guide. > > Since we have a single HTML doc, we could, at first, have an upper toolbar > with all currently supported doc versions: 5.1, 5.0, 4.3, 4.2 > By default, we load current which is the latest version. > > When the user clicks 4.2, we just go to > http://docs.jboss.org/hibernate/orm/4.2/manual/en-US/html_single/ > If he clicks 5.0, we go to > http://docs.jboss.org/hibernate/orm/5.0/manual/en-US/html_single/ > If he clicks 5.1, he navigates to > http://docs.jboss.org/hibernate/orm/5.1/userguide/html_single/Hibernate_User_Guide.html > > Is this what you were thinking of too? > > Vlad > > On Tue, Feb 16, 2016 at 8:54 PM, Emmanuel Bernard > wrote: > >> +1. I like the idea to land on current by default and be able to go to >> older versions of the documentation section if requested. >> >> It will require some work but I do think that it is doable in Awestruct. >> >> Maybe Vlad could spend some time mocking a website in that configuration >> and once we converge start working in the Awestruct implementation. >> I would rather see Vlad working on it as he is our doc focused expert. >> Davide and I can offer Awestruct assistance of course. >> >> > On 12 févr. 2016, at 19:12, Steve Ebersole wrote: >> > >> > Emmanuel, Davide, etal... >> > >> > I think I want to redo that decision to put versioned links on the nav. >> > That was always just a temp solution, as it was the easiest way to add >> > handling for versioned docs. But as I add 5.1 docs we would now have 4 >> > links on the nav for docs. That's starting to get fugly. >> > >> > Instead I'd like to have one link (Documentation) that points to a page >> for >> > "current" documentation. Then from that page (and all the versioned doc >> > pages) I'd like to have a set of links to older docs (or docs by >> version). >> > Ideas on how to best achieve that in our website build? >> > >> > >> >> On Fri, Feb 12, 2016 at 12:05 PM Steve Ebersole >> wrote: >> >> >> >> Vlad, today I will work updating the website for ORM. Versioned >> >> information (documentation) is very difficult to deal with there (imho) >> >> >> >> On Fri, Feb 12, 2016 at 12:01 PM Steve Ebersole >> >> wrote: >> >> >> >>> I went all the way back to 3.0. rsync started >> >>> >> >>> On Fri, Feb 12, 2016 at 11:44 AM Gunnar Morling > > >> >>> wrote: >> >>> >> The more, the better. At least 4.3 is needed as it's the last BV 1.0 >> compatible version. I don't exactly remember what we had there, but I >> suppose all the way back till 3.0. So if you are at 4.2, you are >> almost there :) >> >> 2016-02-12 18:31 GMT+01:00 Steve Ebersole : >> > so far I have downloaded back to 4.2. Should I stop at 5.0? >> > >> > >> > On Fri, Feb 12, 2016 at 11:25 AM Gunnar Morling < >> gun...@hibernate.org> >> > wrote: >> >> >> >> Hey, >> >> >> >> That's weird indeed. Last time I checked (at the time of the HV >> 5.2.3 >> >> release), everything was still in place. >> >> >> >> http://hibernate.org/validator/documentation/ links to the >> following: >> >> >> >> * >> http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html/ >> >> * >> >> http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/html_single/ >> >> * >> >> http://docs.jboss.org/hibernate/validator/5.3/reference/en-US/pdf/hibernate_validator_reference.pdf >> >> * http://docs.jboss.org/hibernate/validator/5.3/api/ (JavaDoc) >> >> >> >> And the same for 5.2 and 4.3. Would be great to restore these ones >> and >> >> the "stable" alias at least; 5.1 and 5.0 would be bonus I suppose. >> >> >> >> Thanks, Steve, if you are taking this over. >> >> >> >> --Gunnar >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> 2016-02-12 18:16 GMT+01:00 Davide D'Alto : >> >>> Links seems to be in the format x.y >> >>> At least looking at the links on >> >>> http://hibernate.org/validator/documentation/ >> >>> >> >>> >> >>> >> >>> On Fri, Feb 12, 2016 at 5:08 PM, Steve Ebersole < >> st...@hibernate.org> >> >>> wrote: >> >>> >> What's the level of versions for the validator docs on the >> server? >> x.y? >> >> On Fri, Feb 12, 2016 at 10:59 AM Steve Ebersole < >> st...@hibernate.org> >> wrote: >> >> > If the old style guides were there after the release, but gone >> since >> > I >> > uploaded yesterday then maybe my upload also affected the >> validator >> > docs. >> > No idea how that could have happened though. >> > >> > Anyway, I checked an the validator release bund
[hibernate-dev] Unresolved issues for 5.0.8
Hi, I'd like to release 5.0.8.Final as soon as tomorrow. I see the following unresolved issues scheduled for 5.0.8: https://hibernate.atlassian.net/browse/HHH-10250 https://hibernate.atlassian.net/browse/HHH-9485 Would there be any problem if I moved those 2 to 5.0.9? Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Unresolved issues for 5.0.8
Hi Gail, for https://hibernate.atlassian.net/browse/HHH-10250 I have just removed it from the 5.0.8 release, we are waiting for a test case. On 16 February 2016 at 21:51, Gail Badner wrote: > Hi, > > I'd like to release 5.0.8.Final as soon as tomorrow. > > I see the following unresolved issues scheduled for 5.0.8: > https://hibernate.atlassian.net/browse/HHH-10250 > https://hibernate.atlassian.net/browse/HHH-9485 > > Would there be any problem if I moved those 2 to 5.0.9? > > Thanks, > Gail > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Unresolved issues for 5.0.8
I just moved the other to 5.0.9 as well. On Tue, Feb 16, 2016 at 4:25 PM andrea boriero wrote: > Hi Gail, > > for https://hibernate.atlassian.net/browse/HHH-10250 I have just removed > it from the 5.0.8 release, we are waiting for a test case. > > > On 16 February 2016 at 21:51, Gail Badner wrote: > > > Hi, > > > > I'd like to release 5.0.8.Final as soon as tomorrow. > > > > I see the following unresolved issues scheduled for 5.0.8: > > https://hibernate.atlassian.net/browse/HHH-10250 > > https://hibernate.atlassian.net/browse/HHH-9485 > > > > Would there be any problem if I moved those 2 to 5.0.9? > > > > Thanks, > > Gail > > ___ > > hibernate-dev mailing list > > hibernate-dev@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
