-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Move Kogito extension out of the Quarkus core repository #7815
Conversation
I assume that the docs need to be removed as well? And perhaps the references to kogito in some yaml metadata files? |
Also, |
@geoand I just removed kogito from ci-actions.yml (and this was also the reason why Misc3 was failing). I cannot find any other yaml referencing it, am I missing something? Also couldn't we leave kogito documentation there even if the extension is now hosted in our codebase? |
I think we should keep the doc in place (and adapt it if needed). |
I believe we can leave the documentation but @maxandersen and @aloubyansky would have more to say about that case. As for the YAML files, I found @maxandersen what does that file do? |
I don't think this failure is related, wdyt @geoand ? |
Yeah, the JVM 13 failure is known (it seems that sometimes CI can't install JVM 13) |
This is +1 from me. I'm just waiting for @maxandersen and @aloubyansky to provide feedback on my question above |
good let's just wait then, thanks! |
Earlier today we talked about this move to be something for 1.4 ? are we saying master is now ready for 1.4 and 1.3.x is branched ?
its used for testing the parsing of a platform - not important and can be kept as is. |
btw. where is the new location ? and is that something that is releasable separate from kogito releases so we neither of us get stuck if we need to update the extension ? |
Master is 1.4. |
ouch we were hoping to include this in 1.3.0 :( |
@gsmet ^ |
No. It won’t be in 1.3. It’s too late. |
I was on my phone so here are more details:
As for the OptaPlanner fix, maybe it should be in a different PR so that we can include it in 1.3.1? That being said, I'm not sure it's the right fix because I'm worried people will have duplicate substitutions if they use both Kogito and OptaPlanner. /cc @ge0ffrey |
@gsmet the Optaplanner fix is only needed in the is PR because Kogito was bumped. It's not needed in the current master. I agree that it is a little too late for |
unfortunately we had delays with releasing 0.8.0. We understand it's too late, we thought there was more time before Final. There is no PR for platform because we were waiting for merging this first; the branch should be here https://github.com/mariofusco/quarkus-platform/tree/k1251 /cc @mariofusco it's fine to merge this to master. As for the proper fix to the OptaPlanner extension, we are already discussing with @ge0ffrey on the matter |
So I am +1 for merging this to master now (the sooner the better to give the most time possible to prepare the rest of the stuff that needs to be done to have Kogito in the platform for 1.4) |
import com.oracle.svm.core.annotate.TargetClass; | ||
|
||
@TargetClass(className = "org.drools.core.rule.builder.dialect.asm.ClassGenerator") | ||
final class Target_org_drools_core_rule_builder_dialect_asm_ClassGenerator { |
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.
-1
This is a substitution that should happen in Kogito (= Drools), not in OptaPlanner. It's not OptaPlanner alone that will suffer from it. OptaPlanner should not work around it, Kogito should fix it. Kogito 0.8.0 is borked, we need a Kogito 0.8.1 release.
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.
If we want to get the PR in, there is no other way. If you folks want to wait for a Kogito release that doesn't suffer from this, that's up to you :).
But if you want it in no, there is no other way
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.
I am willing to comprise to merge it like this for Quarkus 1.3.0 as a temporarily workaround (*), if there's a commitment to revert it by Quarkus 1.3.1 by releasing and using Kogito 0.8.1. @mariofusco wdyt?
(*) Let's add a comment stating that it's a temporarily workaround.
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.
In any case, this PR isn't making it into any 1.3.x line. We are talking purely for 1.4, whether it goes in as is, or with a new Kogito version
@gsmet Master currently is fine, there is no bug there. |
Well, there's no rush. This won't be in either 1.3.0 or 1.3.1. It will be merged to master for 1.4, planned in about a month (so 3 weeks for the CR). That being said, I would recommend to follow up on this soon to avoid having the same issue for 1.4. |
I think it's better if we merge this and then release the hotfix otherwise we can't still update the platform bom, which is the priority |
+1 on merging into master sooner rather than later. |
+1 to merge to master. Any objections @gsmet ? |
import com.oracle.svm.core.annotate.TargetClass; | ||
|
||
@TargetClass(className = "org.drools.core.rule.builder.dialect.asm.ClassGenerator") | ||
final class Target_org_drools_core_rule_builder_dialect_asm_ClassGenerator { |
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.
Why is the class name different from KogitoSubstitutions
?
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.
It doesn't really matter since it's going away really really soon 😎
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.
Well yeah, it's just that it's confusing to look at this class and see another name :)
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.
The idea was that multiple substitutions might have been needed. For example like Netty.
It turned out that it wasn't needed 😊
@ge0ffrey if this is ok for you can you please approve it asap? Thanks. |
If @ge0ffrey approves, I'll merge it right away so the Kogito team can proceed |
@ge0ffrey told he was ok with this here: #7815 (comment) so I would say let's proceed. @mariofusco please follow up on the substitution though. We need a proper fix before 1.4 is released. Thanks all. |
@gsmet thanks. The proper fix is already on kogito master and will be available with kogito 0.8.1. |
@mariofusco did you change the GA of the extension? If so could you provide the new one as it requires a note in the migration guide. Thanks! |
@gsmet the new GA is org.kie.kogito:kogito-quarkus Thank you. |
The extension has been moved to the Kogito repository and is part of the Platform.