-
Notifications
You must be signed in to change notification settings - Fork 612
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-16057 Restore 3rd party integration tests for Wildfly and Tomcat #12365
Conversation
Could not find artifact org.opensaml:opensaml-core:jar:4.2.0 in central (https://repo.maven.apache.org/maven2/) |
According to mvnrepository.com, it seems like version 4.2.0 is only available from the Shibboleth repo: https://mvnrepository.com/artifact/org.opensaml/opensaml-core?repo=shibboleth-releases |
@ryanemerson Sure thing! Lets catch up on Monday as I am on PTO today. |
@ryanemerson Looking at this bit more today, what you could use right-away, is the
Should that be problematic, we can just do the release form the main branch of that project as originally discused. |
@rhusar I just tried again to be sure and I get 500 errors with |
@ryanemerson OK cool - the release is out now - https://github.com/arquillian/arquillian-container-tomcat/releases/tag/1.2.1.Final and released in our nexus (so it might need a minute to sync). Let me know if that works for you :-) |
Thanks @rhusar that worked for me locally. @tristantarrant This should be good to merge once CI has completed. |
- Update jboss repository url in maven-settings.xml - Use maven-settings.xml when executing tests to ensure Wildfly dependencies can be resolved
Thanks @ryanemerson |
https://issues.redhat.com/browse/ISPN-16057
Wildfly version bumped to 32.0
Tomcat tested with 10.1.23. Unfortunately we need to rely on a SNAPSHOT release of
arquillian-tomcat-managed-10
as this has not yet been released, however I'm chasing our good friend @rhusar to see if we can get this released ASAP. This won't affect upstream CI as we don't execute the Tomcat tests here anyway.@tristantarrant I dropped
MemcachedClientIT
as it relies upon theSimpleMemcachedClient
that AFAICT is no longer compatible with the changes on our server and I didn't think was worth the time investment of debugging/fixing.