OptaPlanner native support fixes #1721 #1822
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oscerd
approved these changes
Sep 23, 2020
davsclaus
reviewed
Sep 23, 2020
| import org.optaplanner.core.api.domain.lookup.PlanningId; | ||
|
|
||
| /** | ||
| * adapted from optaplanner quarksu quickstart : |
There was a problem hiding this comment.
quarksu -> quarkus (same for the other places where this is mentioned).
|
Wondering what this means for future CQ releases. I guess we may need to wait for OptaPlanner to bump their bits to the latest Quarkus version before we can proceed with our release? |
zbendhiba
force-pushed
the
1721-optaPlanner
branch
from
309081c
to
aae8afd
Compare
|
@davsclaus @jamesnetherton : I did some changes |
jamesnetherton
force-pushed
the
camel-master
branch
4 times, most recently
from
fdd43ac
to
d8128f5
Compare
github-actions
bot
force-pushed
the
camel-master
branch
3 times, most recently
from
a26946a
to
4788828
Compare
|
@zbendhiba could you please rebase and solve the conflicts? I'd like to review locally, esp. the dependency management part |
zbendhiba
force-pushed
the
1721-optaPlanner
branch
from
aae8afd
to
bf508d8
Compare
|
@ppalaga I rebased, but please do not merge. The tests will fail with graalvm 20.2.0. We should wait for an update of version of extension |
zbendhiba
changed the title
github-actions
bot
force-pushed
the
camel-master
branch
2 times, most recently
from
b515430
to
d13f6cc
Compare
|
I'll set this PR to draft until we have everything in place to merge. |
jamesnetherton
force-pushed
the
camel-master
branch
from
d470e69
to
9253684
Compare
github-actions
bot
force-pushed
the
camel-master
branch
from
9253684
to
2628b89
Compare
jamesnetherton
force-pushed
the
camel-master
branch
from
8e644d2
to
3b7ae6e
Compare
github-actions
bot
force-pushed
the
camel-master
branch
from
3b7ae6e
to
5670648
Compare
jamesnetherton
force-pushed
the
camel-master
branch
3 times, most recently
from
ed1eb3f
to
9715193
Compare
github-actions
bot
force-pushed
the
camel-master
branch
from
9715193
to
9c131ab
Compare
jamesnetherton
force-pushed
the
camel-master
branch
from
9c131ab
to
d40d9c1
Compare
zbendhiba
force-pushed
the
1721-optaPlanner
branch
from
d8d9fc9
to
76c1520
Compare
zbendhiba
force-pushed
the
1721-optaPlanner
branch
from
76c1520
to
b80eca8
Compare
zbendhiba
changed the title
|
Could you please resolve the conflicts, @zbendhiba ? |
|
@ppalaga yes |
zbendhiba
force-pushed
the
1721-optaPlanner
branch
from
b80eca8
to
8999db2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
native support of optaplanner using optaplanner quarkus extension and recent support of SolverManager in Camel.