Sure. A couple points:
* integration is being deprecated and we wouldn't accept any updates to that
* integration-arquillian is what you want to focus on. There's already a
simple way to set the port through the arquillian.xml and should be easy to
add a sys prop there. One remaining thing is that a lot of tests just
assumes it to run on localhost:8081 instead of pulling the URL properly
from the suitecontext so you'd need to go through quite a lot of tests to
make it work properly
On 13 July 2017 at 13:54, Wim Vandenhaute <wim.vandenhaute(a)gmail.com> wrote:
Hey list,
For a customer of mine, I submitted a few PR's and now have to dig into a
changed behavior on one of the keycloak integration tests.
Sadly enough, on the dev machine I am working on @ my customer's site, the
port 8081 is in use by a McAfee service program which I cannot kill.
Hence my question, would it be acceptable if I made a PR with an effort to
make 8081 ( and I think 8082 also ) configurable via e.g. a maven property
so I can override this when running the tests from that dev machine?
Is an effort planned for this?
Just so I do not waste too much time on this one :)
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev