On 24 January 2018 at 15:46, Steve Ebersole <st...@hibernate.org> 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 <sa...@hibernate.org> wrote: >> >> On 24 January 2018 at 15:33, Steve Ebersole <st...@hibernate.org> 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.concurrent.TimeoutException >> > >> > ? >> >> If your TimeoutException was caused by the same underlying issue as >> Vlad and Chris had hit.. yes. >> >> > >> > >> > On Wed, Jan 24, 2018 at 9:03 AM Chris Cranford <ch...@hibernate.org> >> > wrote: >> >> >> >> 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 <sa...@hibernate.org> >> >> > wrote: >> >> >> 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 configured" for >> >> >> Maven, for >> >> >> the current user. If the current user's configuration doesn't list >> >> >> the >> >> >> JBoss >> >> >> nexus it will ignore the locally cached artifacts, even if we made >> >> >> sure >> >> >> to >> >> >> download them during provisioning. >> >> >> >> >> >> I'm looking for settings we might use today, if I fail I'll revert >> >> >> it. >> >> >> >> >> >> On 24 Jan 2018 13:17, "Steve Ebersole" <st...@hibernate.org> wrote: >> >> >> >> >> >> 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 <sa...@hibernate.org> >> >> >> 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 JBoss Nexus >> >> >>> repository enabled in your *Maven* configuration. (Yes, even though >> >> >>> we >> >> >>> use Gradle..) >> >> >>> >> >> >>> For the time being could you create a ~/.m2/settings.xml >> >> >>> >> >> >>> having the content you can copy from: >> >> >>> - >> >> >>> >> >> >>> >> >> >>> https://raw.githubusercontent.com/hibernate/hibernate-search/8f7e87bf282877a7a5554035abb709cc9813fec2/settings-example.xml >> >> >>> >> >> >>> This is just a temporary solution so that you're not stuck today, >> >> >>> while I'm looking for a better fix. >> >> >>> >> >> >>> For details, see: >> >> >>> - >> >> >>> >> >> >>> http://lists.jboss.org/pipermail/wildfly-dev/2018-January/006335.html >> >> >>> >> >> >>> Thanks, and sorry for the inconvenience! >> >> >>> >> >> >>> Sanne >> >> >>> _______________________________________________ >> >> >>> 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
