-
Notifications
You must be signed in to change notification settings - Fork 91
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
Kogito 1.14.1.Final + OptaPlanner 8.14.1.Final #397
Kogito 1.14.1.Final + OptaPlanner 8.14.1.Final #397
Conversation
@evacchi any idea here ? EDIT: Note that this is targeting platform 2.5 as I know that it would fail on 2.6 ... |
meaning is there an upstream quarkus issue to track please? |
You may need to propagate the |
It was fixed in 2.5.1.Final quarkusio/quarkus#21673 |
Let's try with this change
|
@radtriste could you apply the change? |
Didn't help it seems. I'll check what's going on. |
Ok, here is what happens. The test generates a new project and executes a Maven command to verify it can be built. The staging repository that was added to the platform POM isn't available for the created project. With the So, the way to make it work will be to add the staging repo not to the platform's POM file but to the |
did it. but FYI, Kogito artifacts have been released already, so this should not be needed anymore. But good to know for the next time ;) |
If they are on Central already then the change will be useless. |
I'm releasing Quarkus 2.5.2.Final tomorrow morning early Paris time so if you want this in, we need the staging repo gone and the PR rebased and regenerated with |
Given the late time, I will do it and see how it goes. |
The artifacts are not available yet unfortunately. |
Platform release will probably be around 2pm so I'll check tomorrow morning. I think it's going to be a pain to rebase so I will rebase it this evening. |
It will conflict with #402 so I will rebase it once the other PR is merged. |
I just force pushed a rebase on top of latest 2.5. |
BTW, it'd be better to use
instead of
|
The artifacts still aren't in Central. But I could make progress with these changes:
However, I still got one failure
Which means the necessary snapshot files will need to be copied to the resources. |
A couple of options to improve the setup in perspective:
|
trying with https://repository.jboss.org/nexus/content/groups/public/ which is were you can find current 1.14.1 artifacts |
Artifacts are on Jboss Nexus but seems they were not sync on Central. Asking Jboss nexus team about that |
This does not work for |
Yes, it's kind of weird. Perhaps, omit |
Unless you copy the snapshots similar to https://github.com/quarkusio/quarkus-platform/blob/main/pom.xml#L214-L217 it won't work right now. If you don't want to do that, you can simply skip the test for now. |
@evacchi @radtriste could you consider moving to s01.oss.sonatype.org to deploy your releases? It's just impossible to do any sort of release planning with repository.jboss.org. |
@gsmet I do get it but for now all projects in bsig are deployed through JBoss Nexus. We do have an issue though: https://issues.redhat.com/browse/BXMSPROD-1513 Technically I don't think there is a big difference as sonatype is a Nexus behind so most commands should work there but it is true that this is an external repository and we would depend on it ... |
@radtriste I can understand that but from my experience repository.jboss.org sync is too unreliable to plan anything. I think it's too late to have 1.14.1 into 2.5.2 now. But we really need a new release for 2.6 so we'd better get it sync on time... /cc @evacchi |
@radtriste the timeline for Quarkus 2.6 is
which means that we have between 15 and 22 to release 1.14.2. As far as I know the fix by @manstis can be easily backported and it is backwards-compatible to 2.5, so we can even start a release immediately after merging that (building against Quarkus 2.5) Is that correct @gsmet ? |
@evacchi yes, that's my understanding too. Just be careful, I release on 22nd so you have until 21st. You can build with 2.5 and you can already test with 2.6.0.CR1 (platform main was already updated). |
OK, still nothing on Central. Officially too late. |
The artifacts are on Central now. |
Per discussion with the Kogito team, we will merge the next release instead. |
No description provided.