[hibernate-dev] Hibernate ORM modules for Wildfly 11

[Steve Ebersole]

Then I think we should update 5.2 as well, but that creates an interesting
concern in that the published artifact name would change if I understand
correctly because it would change the artifact's classifier from
`wildfly-10-dist` to `wildfly-11-dist`.  Things that refer to this artifact
as a dependency would no longer work.

On Tue, Aug 29, 2017 at 11:05 AM Gail Badner <gbadner at redhat.com> wrote:

> Hibernate ORM 5.1.x is in WF 11.
>
> On Mon, Aug 28, 2017 at 4:20 PM, Steve Ebersole <steve at hibernate.org>
> wrote:
>
>> What version of Hibernate does WF 11 include?
>>
>> On Mon, Aug 28, 2017, 5:18 PM Gail Badner <gbadner at redhat.com> wrote:
>>
>>> This should be backported to 5.1 as well, shouldn't it?
>>>
>>> On Sun, Aug 27, 2017 at 2:27 PM, Steve Ebersole <steve at hibernate.org>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Thanks Sanne!
>>>>
>>>> On Sun, Aug 27, 2017 at 4:06 PM Sanne Grinovero <sanne at hibernate.org>
>>>> wrote:
>>>>
>>>> > Thanks Steve!
>>>> > for reference JIRA and PR:
>>>> >  - https://hibernate.atlassian.net/browse/HHH-11950
>>>> >  - https://github.com/hibernate/hibernate-orm/pull/1994
>>>> >
>>>> > I also just noticed that supporting only the latest is consistent with
>>>> > the expectations we set in the documentation.
>>>> >
>>>> > Thanks,
>>>> > Sanne
>>>> >
>>>> >
>>>> > On 27 August 2017 at 17:06, Steve Ebersole <steve at hibernate.org>
>>>> wrote:
>>>> > > I personally agree that we should only be maintaining a single
>>>> slice of
>>>> > the
>>>> > > version matrix here... a given ORM version against the latest
>>>> Wildfly
>>>> > > version.
>>>> > >
>>>> > >
>>>> > > On Sun, Aug 27, 2017, 7:31 AM Sanne Grinovero <sanne at hibernate.org>
>>>> > wrote:
>>>> > >>
>>>> > >> Hi all,
>>>> > >>
>>>> > >> WildFly 11 is coming: the version 11.0.0.CR1 was just released last
>>>> > week.
>>>> > >>
>>>> > >> The jipijapa integration point is slightly different.
>>>> > >>
>>>> > >> It shouldn't be hard to patch the current ORM build for this, but
>>>> I'm
>>>> > >> wondering if we just want to update the target WF version, or start
>>>> > >> producing sets for both WildFly 10 and WildFly 11 ?
>>>> > >>
>>>> > >> Personally as soon as we can move all integration tests to WildFly
>>>> 11,
>>>> > >> I won't be interested in maintaining WF10 compatibility for the 5.2
>>>> > >> branch of Hibernate ORM (and related projects) so I'd be inclined
>>>> to
>>>> > >> simply update the WF version.
>>>> > >>
>>>> > >> The motivations:
>>>> > >>  - people are asking already for ORM modulesets for WF11
>>>> > >>  - these modules missing are a blocker for producing modulests for
>>>> out
>>>> > >> other projects, e.g. Hibernate Search
>>>> > >>  - people are asking for latest Hibernate Search modulesets for
>>>> WF11 as
>>>> > >> well..
>>>> > >>
>>>> > >> I'd treat this with urgency: while I don't expect any compatibility
>>>> > >> issue with WF11 it would be nice to be able to test it all before
>>>> it's
>>>> > >> released as .Final
>>>> > >>
>>>> > >> Thanks,
>>>> > >> Sanne
>>>> > >> _______________________________________________
>>>> > >> hibernate-dev mailing list
>>>> > >> hibernate-dev at lists.jboss.org
>>>> > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>> >
>>>> _______________________________________________
>>>> hibernate-dev mailing list
>>>> hibernate-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>
>>>
>>>
>