-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Upgrade to ANTLR 4.10.1 (for the ANTLR 4.x series) #27298
Conversation
This comment has been minimized.
This comment has been minimized.
@evacchi | @mariofusco | @lucamolteni hi :) Looks like I'm going to need your help. Apparently Could you all upgrade to |
This comment has been minimized.
This comment has been minimized.
fyi @tarilabs |
hi @Sanne I might have limited ability to follow this through as I'm on PTO: Antlr4 is a bit delicate for DMN as it has some ties also with some GWT work, so I will be keeping 🤞 but worth giving it a shot, let's see what Jenkins says 🙃 Tracked with https://issues.redhat.com/browse/DROOLS-7105 and derivatives: |
we've merged a temporary workaround for Kogito in the quickstarts: [Not opening an issue to get it cleaned up later as I'm sure we'll notice when Kogito will update] With the quickstarts no longer breaking I think we can merge this - doing a last CI run. |
damn this one is going to be very annoying:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the quickstarts no longer breaking I think we can merge this - doing a last CI run.
@Sanne I disagree we can merge it. We need a clear plan for Kogito to upgrade before doing so as the Platform will use only one version and we can't expect Platform consumers to have to override the version locally.
So:
- we need to make sure Kogito can upgrade
- define in which version we upgrade and coordinate the upgrades to make sure the Platform is consistent
You might already have a plan but if so let's make it clear in this PR.
@gsmet sure I understand; my assumption is that the Kogito upgrade will be fairly simple, and it's going to be easier for them to test things if we do the change first - since it's a downstream project. If it turns out it's a hell of a problem we can revert here; but it would be simpler to try to keep going so to identify other issues with it. Already found a critical issue with the MSSQL JDBC driver so we might need to hold anyway. Wondering now why we didn't hit it in the ORM testsuite?! Seems related with native image's flow analsys, it seems the check is possibly in a code path not being triggered by the tests in Hibernate ORM. |
This comment has been minimized.
This comment has been minimized.
Kogito Quarkus is a downstream project, not Kogito. Kogito is a different upstream. Thus why we need to coordinate and make sure we upgrade together. Given the SQL Server issue, let's make sure we can upgrade before pulling the trigger for Kogito too. |
FYI for as much as I can verify at present, on Drools DMN engine side we're ready to bump to Antlr 4.10 as you requested, ref this https://github.com/kiegroup/drools/pull/4614#issuecomment-1227070425 for the build errors in case let me know if I missed some CI-related considerations |
Rebased, and updated to It seems runtime-compatible with |
This comment has been minimized.
This comment has been minimized.
No idea, no. |
I'm having fun with Pact and the Antlr upgrade too, @knutwannheden - we raised pact-foundation/pact-jvm#1615. It may be something a Pact Quarkus extension can fix, since Pact-Quarkus-Antlr seems to be a recurring compatibility issue (I spotted you raised pact-foundation/pact-jvm#1380 a while ago). I've raised quarkiverse/quarkus-pact#1 to track it for the extension. |
I think it will. The ATN changed from 3 (used by 4.9.2) to 4 (used by 4.11.1) in Antlr 4.10. So as I understand it, that means 4.10 should be compatible with 4.11. |
@holly-cummins That sounds about right. Thanks for the heads up. I will look into the new extension and may be able to provide some feedback, since we've already used Pact consumer and provider tests in Quarkus projects for quite some time now. |
apologies, I don't remember about the plan here. @gsmet is it suitable for merging now ? Rebased to get a fresh opinion from CI. |
This comment has been minimized.
This comment has been minimized.
Failing Jobs - Building af0973b
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
|
The error mentions KIE:
We're aware that this will break KIE but agreed with the team to merge this anyway, they'll catch up and updat ANTLR on their side as well soon. |
Actually that's exactly the same module that I had patched months ago to prevent this very issue. I know this worked, now I'm confused about why that would no longer be effective ? |
I tried to build it all locally and I could use some suggestion as to why these versions wouldn't get applied on CI ; commenting here as well: |
Could it be that the CI failure pertains to another quickstart? 🤔 Sorry just wild guess based on comments as I can access only on mobile atm |
@tarilabs you're right, I was blind yesterday night :) thanks. I'll send a PR shortly. |
thanks to you @Sanne , sorry I couldn't turn around faster here before you. Thanks again for the related PR |
This is in preparation of Hibernate ORM 6: we'll require this version, so might as well try to prepare for that, in case there's other projects that need to adapt.
N.B. versions v3 and v4 of ANTLR use a different package name, therefore this has no impact on users of ANTLR v3.x and previous.