1:23 a.m.
If you haven’t already, please send in a PR updating your component to Final status, as we
hope to release 9 Final this month.
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
1:21 p.m.
Hibernate Search / Infinispan Query modules (and its dependencies) need a complete
overhaul -- as they are a complete mess / useless atm.
So I'm just wondering who's gonna take this over?
Sanne / Gustavo?
-Ales
On 11 Apr 2015, at 01:23, Jason Greene
<jason.greene(a)redhat.com> wrote:
If you haven’t already, please send in a PR updating your component to Final status, as
we hope to release 9 Final this month.
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
8:15 p.m.
Hi Ales,
that modules refactoring is tracked by WFLY-4232.
Note that it was marked "just" as an improvement (to minimize
dependencies) as there never was an intention to expose the Infinispan
Query features to users. I'll raise the priority (and fix it) since it
seems CapeDwarf needs it but discussing with Tomaž we've found a
better solution for post-WF9; see also the thread "Feature-packs,
versions / module slots and independent release cycles", that
describes how we should solve it in future.
Sanne
On 13 April 2015 at 12:21, Ales Justin <ales.justin(a)gmail.com> wrote:
Hibernate Search / Infinispan Query modules (and its dependencies)
need a complete overhaul -- as they are a complete mess / useless atm.
So I'm just wondering who's gonna take this over?
Sanne / Gustavo?
-Ales
> On 11 Apr 2015, at 01:23, Jason Greene <jason.greene(a)redhat.com> wrote:
>
> If you haven’t already, please send in a PR updating your component to Final status,
as we hope to release 9 Final this month.
>
> Thanks!
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
10:21 a.m.
With latest Ispn 7.2.0.CR1 and HS 5.2.0.Beta1 I get a ton of exceptions when upgraded in
WF9.0.0.Beta2.
(not that it’s unexpected, just pointing it out for Paul to fix it :-)
* https://gist.github.com/alesj/9260503671f88d010d6a
<https://gist.github.com/alesj/9260503671f88d010d6a>
-Ales
On 20 Apr 2015, at 20:15, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
Hi Ales,
that modules refactoring is tracked by WFLY-4232.
Note that it was marked "just" as an improvement (to minimize
dependencies) as there never was an intention to expose the Infinispan
Query features to users. I'll raise the priority (and fix it) since it
seems CapeDwarf needs it but discussing with Tomaž we've found a
better solution for post-WF9; see also the thread "Feature-packs,
versions / module slots and independent release cycles", that
describes how we should solve it in future.
Sanne
On 13 April 2015 at 12:21, Ales Justin <ales.justin(a)gmail.com> wrote:
> Hibernate Search / Infinispan Query modules (and its dependencies) need a complete
overhaul -- as they are a complete mess / useless atm.
>
> So I'm just wondering who's gonna take this over?
> Sanne / Gustavo?
>
> -Ales
>
>> On 11 Apr 2015, at 01:23, Jason Greene <jason.greene(a)redhat.com> wrote:
>>
>> If you haven’t already, please send in a PR updating your component to Final
status, as we hope to release 9 Final this month.
>>
>> Thanks!
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
4:57 p.m.
Are there plans to update Ispn to 7.2.x version in latest WF?
@Paul, Rado ^^
-Ales
On 20 Apr 2015, at 20:15, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
Hi Ales,
that modules refactoring is tracked by WFLY-4232.
Note that it was marked "just" as an improvement (to minimize
dependencies) as there never was an intention to expose the Infinispan
Query features to users. I'll raise the priority (and fix it) since it
seems CapeDwarf needs it but discussing with Tomaž we've found a
better solution for post-WF9; see also the thread "Feature-packs,
versions / module slots and independent release cycles", that
describes how we should solve it in future.
Sanne
On 13 April 2015 at 12:21, Ales Justin <ales.justin(a)gmail.com> wrote:
> Hibernate Search / Infinispan Query modules (and its dependencies) need a complete
overhaul -- as they are a complete mess / useless atm.
>
> So I'm just wondering who's gonna take this over?
> Sanne / Gustavo?
>
> -Ales
>
>> On 11 Apr 2015, at 01:23, Jason Greene <jason.greene(a)redhat.com> wrote:
>>
>> If you haven’t already, please send in a PR updating your component to Final
status, as we hope to release 9 Final this month.
>>
>> Thanks!
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
11:45 a.m.
Hi Ales,
the current plan is to stick with 7.1 (currently we are pulling
7.1.1.Final) due to timing since we are targeting WF final at the end of
month and Infinispan 7.2 likely won't be final in time (and yes, simply
dropping in 7.2.0.CR1 won't work since it won't even compile).
Rado
On 22/04/15 16:57, Ales Justin wrote:
Are there plans to update Ispn to 7.2.x version in latest WF?
@Paul, Rado ^^
-Ales
> On 20 Apr 2015, at 20:15, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> Hi Ales,
>
> that modules refactoring is tracked by WFLY-4232.
>
> Note that it was marked "just" as an improvement (to minimize
> dependencies) as there never was an intention to expose the Infinispan
> Query features to users. I'll raise the priority (and fix it) since it
> seems CapeDwarf needs it but discussing with Tomaž we've found a
> better solution for post-WF9; see also the thread "Feature-packs,
> versions / module slots and independent release cycles", that
> describes how we should solve it in future.
>
> Sanne
>
> On 13 April 2015 at 12:21, Ales Justin <ales.justin(a)gmail.com> wrote:
>> Hibernate Search / Infinispan Query modules (and its dependencies) need a
complete overhaul -- as they are a complete mess / useless atm.
>>
>> So I'm just wondering who's gonna take this over?
>> Sanne / Gustavo?
>>
>> -Ales
>>
>>> On 11 Apr 2015, at 01:23, Jason Greene <jason.greene(a)redhat.com>
wrote:
>>>
>>> If you haven’t already, please send in a PR updating your component to Final
status, as we hope to release 9 Final this month.
>>>
>>> Thanks!
>>> --
>>> Jason T. Greene
>>> WildFly Lead / JBoss EAP Platform Architect
>>> JBoss, a division of Red Hat
>>>
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
2:10 p.m.
Is there going to be a candidate release? The reason I released a CR of
Remoting JMX was to try and give an opportunity for community to test
the reported bugs are fixed in the next WildFly CR before all are tagged
.Final.
On 11/04/15 00:23, Jason Greene wrote:
If you haven’t already, please send in a PR updating your component
to Final status, as we hope to release 9 Final this month.
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3:25 p.m.
Yes but a very short one. So far we have had nothing major on Beta, so I think it's
pretty solid. It would mainly be to shake out any release errors.
Ideally we wouldn't be updating all deps unless there was an actual bug we had to fix.
Is there a quality concern or is it more just not jumping right to final for your
component?
On Apr 13, 2015, at 7:11 AM, Darran Lofthouse
<darran.lofthouse(a)jboss.com> wrote:
Is there going to be a candidate release? The reason I released a CR of
Remoting JMX was to try and give an opportunity for community to test
the reported bugs are fixed in the next WildFly CR before all are tagged
.Final.
> On 11/04/15 00:23, Jason Greene wrote:
> If you haven’t already, please send in a PR updating your component to Final status,
as we hope to release 9 Final this month.
>
> Thanks!
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3:31 p.m.
On 13/04/15 14:25, Jason T. Greene wrote:
Yes but a very short one. So far we have had nothing major on Beta,
so I think it's pretty solid. It would mainly be to shake out any release errors.
Ideally we wouldn't be updating all deps unless there was an actual bug we had to
fix. Is there a quality concern or is it more just not jumping right to final for your
component?
No real quality concern, bug fixes affected connection state so would
just be nice for an opportunity for community to also report back.
I can tag now if you really want but also not a big deal to tag at an
agreed date - it is a genuine candidate for release.
> On Apr 13, 2015, at 7:11 AM, Darran Lofthouse <darran.lofthouse(a)jboss.com>
wrote:
>
> Is there going to be a candidate release? The reason I released a CR of
> Remoting JMX was to try and give an opportunity for community to test
> the reported bugs are fixed in the next WildFly CR before all are tagged
> .Final.
>
>
>> On 11/04/15 00:23, Jason Greene wrote:
>> If you haven’t already, please send in a PR updating your component to Final
status, as we hope to release 9 Final this month.
>>
>> Thanks!
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
3291
days inactive
3304
days old
8 comments
6 participants
participants (6)
-
Ales Justin -
Darran Lofthouse -
Jason Greene -
Jason T. Greene
-
Radoslav Husar -
Sanne Grinovero