-
Notifications
You must be signed in to change notification settings - Fork 2
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
Merge for version 3.0.0 #24
base: master
Are you sure you want to change the base?
Conversation
… configuration. Taken from: stianh/gradle-jaxb-plugin@ff91275 This enables other developers to locally do a gradle install of their own versions without being stopped because the build want to sign the artifacts first. To enable signing now, one must set the project property sign, like this: gradle -Psign
cleanEclipse.taskDependencies.values is no longer supported with Gradle 4.7. Since we no longer support Eclipse, we remove this section.
Feature/12 gradle4
…uild or branch is somehow corrupt, ignore it in this case and log an error.
Update with Master
…mportant branches
…-or-branch' of https://github.com/scenarioo/scenarioo-java into feature/14-fix-failing-on-corrupt-build-or-branch
…pt-build-or-branch #14 Fix loading of builds and branches to not fail with corrupt data
…tations :-)" accidentialy commited This reverts commit 5852626
… 5 assertThrows. This is an optional commit. If we decide not to increase the language level, then we can revert this commit and still merge the basic JUnit 5 migration.
…hangelog), the version is increased to 3.0.0-SNAPSHOT.
Feature/20 junit5
- Added JAXB dependencies that were removed from Java 11 - Needed to update Gradle version to 5.6
This reverts commit a2c0ac0
- change from 1.6 to 1.8 compatibility is easier to maintain for users - build is still ready for Java 11 because JAXB dependencies are supplied
Support JDK 11 with new writer version
Use try-with-resources for cleaner code. Fixes #17.
Code clean up (IntelliJ suggestions). Closes #1
Upgrade gradle to version 6.7.1. This streamlines scenarioo main and …
Feature/migrate maven publish
Feature/17 slf4j
@davidlahner I remember there were a lot of planned changes with the next version of
What do you think? If ok, I would do a release of the library version, after I tested, that the bugfixed version of Scenarioo would still work with version 3. |
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.
@mi-we: I agree, that makes a lot of sense. The current published version is way out of date (java-version, etc.).
…rface Feature/11 improve details interface
see what has changed