Hi all,
especially Chris, and anyone else having problems with the integration
tests using WildFly,
the problem seems to be caused by not having the JBoss Nexus
repository enabled in your *Maven* configuration. (Yes, even though we
use Gradle..)
For the time being could you create a ~/.m2/setting
Hello,
We just released Hibernate Search 5.9.0.CR1, with WildFly feature packs and
various bugfixes.
This is the last step before 5.9 is released. Be sure to check it out so
you can share your thoughts with us before the release!
You can find more information about 5.9.0.CR1 on our blog:
http://
I'm confused. You're saying it's not enough to include it in the Gradle
script?
On Wed, Jan 24, 2018, 5:05 AM Sanne Grinovero wrote:
> Hi all,
> especially Chris, and anyone else having problems with the integration
> tests using WildFly,
>
> the problem seems to be caused by not having the JBo
That's right :(
Including it in the build script gets our provioning plugin to know how to
resolve things, and all works fine in the phase of creating the server
copy.
But next the produced Wildfly server starts in a new JVM, entirely new
context, and expects to find the dependencies "as configur
This is fixed now: HHH-12250
You should all be free to remove JBoss Nexus from your settings.xml
again, if you prefer.
Thanks
On 24 January 2018 at 13:33, Sanne Grinovero wrote:
> That's right :(
>
> Including it in the build script gets our provioning plugin to know how to
> resolve things, a
Thanks Sanne.
On 01/24/2018 10:01 AM, Sanne Grinovero wrote:
> This is fixed now: HHH-12250
>
> You should all be free to remove JBoss Nexus from your settings.xml
> again, if you prefer.
>
> Thanks
>
>
> On 24 January 2018 at 13:33, Sanne Grinovero wrote:
>> That's right :(
>>
>> Including it in
To be clear... this fixes errors like:
org.hibernate.wildfly.integrationtest.HibernateEnversOnWildflyTest >
classMethod FAILED
org.jboss.arquillian.container.spi.client.container.LifecycleException
Caused by: java.util.concurrent.TimeoutException
?
On Wed, Jan 24, 2018 at 9:03 AM Ch
On 24 January 2018 at 15:33, Steve Ebersole wrote:
> To be clear... this fixes errors like:
>
> org.hibernate.wildfly.integrationtest.HibernateEnversOnWildflyTest >
> classMethod FAILED
> org.jboss.arquillian.container.spi.client.container.LifecycleException
> Caused by: java.util.conc
On 24 January 2018 at 15:46, Steve Ebersole wrote:
> The stacktrace did not say. Anyway, I pulled and the errors in those tests
> are gone. Thanks!
Great to hear it confirmed! Thank you
>
> On Wed, Jan 24, 2018 at 9:43 AM Sanne Grinovero wrote:
>>
>> On 24 January 2018 at 15:33, Steve Ebersol
The stacktrace did not say. Anyway, I pulled and the errors in those tests
are gone. Thanks!
On Wed, Jan 24, 2018 at 9:43 AM Sanne Grinovero wrote:
> On 24 January 2018 at 15:33, Steve Ebersole wrote:
> > To be clear... this fixes errors like:
> >
> > org.hibernate.wildfly.integrationtest.Hib
Do y'all mind then if I get rid of the hibernate/bundles[1] repo? It's a
"generic" Artifactory repo meant to hold release bundles. ORM[2] and
OGM[3] both have played with it, as we both have versions published there.
But for ORM at least those are also on SourceForge and its not important
that I
no objection
On 24 January 2018 at 15:51, Steve Ebersole wrote:
> Do y'all mind then if I get rid of the hibernate/bundles[1] repo? It's a
> "generic" Artifactory repo meant to hold release bundles. ORM[2] and
> OGM[3] both have played with it, as we both have versions published there.
> But f
Sure you can get rid of it.
The only versions of OGM there is a very old one people shouldn't use.
Thanks!
On Wed, Jan 24, 2018 at 4:58 PM, andrea boriero
wrote:
> no objection
>
> On 24 January 2018 at 15:51, Steve Ebersole wrote:
>
>> Do y'all mind then if I get rid of the hibernate/bundles
Fine with me.
On 01/24/2018 11:23 AM, Guillaume Smet wrote:
> Sure you can get rid of it.
>
> The only versions of OGM there is a very old one people shouldn't use.
>
> Thanks!
>
> On Wed, Jan 24, 2018 at 4:58 PM, andrea boriero
> wrote:
>
>> no objection
>>
>> On 24 January 2018 at 15:51, Steve
Follow up question...
Snapshots are only ever hosted on the JBoss snapshot repo. They are never
sync'ed to Central. As such we are not under the same validation
constraints. So should we publish Javadocs for snapshot builds? Not doing
so would speed up the CI jobs a bit.
On Tue, Jan 2, 2018 a
People seem to be relying on me to backport to 5.2. From a product
standpoint, there is no need to backport to 5.2 anymore once 5.3.0 is
released. Maybe 5.3.0 and 5.2.13 should be released together, with 5.2.13
being the last 5.2 release.
>From an earlier thread, it sounds like there is concern ou
For what it's worth, +1 on this. At least back in the day, we'd
continue to backport bugfixes to the previous minor release, until a new
final minor release was deployed. That was the responsibility of
whoever was committing to master. Since the baselines were typically
"close enough", commi
17 matches
Mail list logo
