Massive dependency updates #3
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
|
Hello @nightscape, as a matter of fact, Kagera was the inspiration and the base of Baker in the early days of development. I had the idea of a catalogue-driven fulfilment process for ING and @merlijn already had developed Kagera in one of his previous projects. At some point, Merlijn decided to merge Kagera into Baker. This fork remained. |
|
Seems like the MR breaks the build pipeline. I can also reproduce locally. @nightscape, can you check? |
scala-steward
pushed a commit
to scala-steward/kagera
that referenced
this pull request
Sep 11, 2021
Massive dependency updates
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.
I'm currently experimenting with using Kagera instead of Baker for a use case where Baker does not seem suitable (ing-bank/baker#541).
I've brought the dependencies more or less up-to-date so that the project compiles and tests run under Scala 2.12.
Another question in that regard:
Why wasn't Kagera used as a base library for Baker?
It would seem useful to have one library that is focused on Petri Nets themselves and then build Akka, recipe compilation, etc. on top of that.