Restore running Maven checks by default#11309
Conversation
losipiuk
left a comment
There was a problem hiding this comment.
LGTM.
Yet as discussed offline it may be better to add trino-exchange as a provided dependency of trino-testing. And add it for real only to modules which actually make use of the classes from there (trino-tests and maybe sth else).
I did not verify if this approach would work - but seems as it should.
I would suggest removing it from there. |
|
Let me try: #11311 |
|
Can you please rebase on top of #11311 ? |
c225481 to
d02dbeb
Compare
d02dbeb to
c60280b
Compare
|
@nineinchnick see red CI |
c60280b to
d39cd1a
Compare
I swear I ran a build locally to check it first ... Rebased on the latest master and I checked locally again. |
b66c7ab to
4dea871
Compare
`trino-exchange` has lots of dependencies, and `trino-testing` is used in all modules. This causes classpath conflicts which were not detected because maven dependency checker was not being run (fixed in airbase 122). This commit adds a bit of code duplication, but reduces dependencies.
Was renamed in f85eaab.
4dea871 to
1558a7f
Compare
Airbase since 120 does not enable plugins marked as skipped using `air.check.skip-*` properties, but it wasn't properly handling property expansion. Airbase 122 does not enable check plugins only when `air.check.skip-all` is set, and skips them using configuration in other cases.
1558a7f to
0961b0a
Compare
|
added fixes for new imports ordering violations from #11312 |
Description
Restore running Maven checks by default.
Since it was disabled for two days, also fix:
trino-exchangetotrino-tests;Related issues, pull requests, and links
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: