-
Notifications
You must be signed in to change notification settings - Fork 3k
Make rest-client aware of deployment profiles #4984
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
Conversation
@cescoffier @kenfinnigan given that the only proper way to test this is to add a test that includes |
Stupid question: we don't have other areas doing the same mistake? It looks like an honest one. |
That's a great question, let me check |
We have a lot of them unfortunately... I am not sure what we should do so close to a release... |
Instead of tests, is there a maven plugin we can use that looks for the bad way to retrieve config and fails the build if it's present? |
I can fix this one as part of my REST TCK work, as it needs to be rebased anyway |
@kenfinnigan not sure, but that would fail master unfortunately because there are places where the other way of doing things is valid and is being used and some where I'm not sure. This close to release I am very hesitant to make such across the board changes |
Wasn't suggesting now, just trying to think of a way to prevent them from being added in the future |
@kenfinnigan yes, we will need to address that for sure |
20e5c4a
to
3b73864
Compare
CI failure seems to be due to Azure infra. I'll restart the failing tests once the others finish |
I've included this fix in the REST TCK fixes, so we could close |
OK, closing as #4954 includes the fix this PR proposed |
Fixes: #4983