-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISPN-5009 Rebase server to WildFly 8.2 #3096
ISPN-5009 Rebase server to WildFly 8.2 #3096
Conversation
@tristantarrant Fair few failures |
9e29a4d
to
10fb227
Compare
Modified the server testsuite to transform based on the new 2.2 domain schema version |
@galderz @tristantarrant ready to integrate? |
It is for me |
testing and pushing... |
@tristantarrant got 2 failures:
|
Still errors, please adjust labels accordingly. |
TeamCity Infinispan :: Pull requests monitor Build 8052/tristantarrant:ISPN-5009/WildFly8.2 outcome was FAILURE Failed tests
|
TeamCity Infinispan :: Pull requests monitor Build 8066/tristantarrant:ISPN-5009/WildFly8.2 FAILURE Failed tests detected
|
FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8079/tristantarrant:ISPN-5009/WildFly8.2 for 10fb227 Failed tests detected
|
I'm looking at those two failures |
Had a look but could not see anything obviously wrong with it. |
- Also micro bumps of Netty and Scala
10fb227
to
2cef74c
Compare
Hey @tristantarrant, @galderz ! For some reason I noticed that the beans are registered a bit differently in Weld's 2.2 manual [2]. I will try this approach and ask Weld Team for advice if needed. In the meantime I would suggest turning off those tests and creating Jira for them (please feel free to assign me to this issue). [1] https://gist.github.com/slaskawi/ac83d30a62a8d12550f4 |
@slaskawi Rather than disabling the tests, let's close this PR and open a new one when the upgrade to WF 8.2 works as expected. Closing this PR for the time being. |
https://issues.jboss.org/browse/ISPN-5009