Skip to content
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

Open
wants to merge 60 commits into
base: master
Choose a base branch
from
Open

Merge for version 3.0.0 #24

wants to merge 60 commits into from

Conversation

bruderol
Copy link
Member

see what has changed

bruderol and others added 30 commits November 4, 2017 16:45
… 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.
…uild or branch is somehow corrupt, ignore it in this case and log an error.
…pt-build-or-branch

#14 Fix loading of builds and branches to not fail with corrupt data
bruderol and others added 23 commits December 2, 2018 21:06
…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.
- Added JAXB dependencies that were removed from Java 11
- Needed to update Gradle version to 5.6
- 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 …
@mi-we
Copy link
Member

mi-we commented Nov 13, 2022

@davidlahner I remember there were a lot of planned changes with the next version of scenarioo-java. I wanted to fix the log4j vulnerability on master first but now I believe that it would be even better to release the current state of develop as version 3 and not provide a separate bugfix release 2.1.x for the following reasons:

  • The log4j vulnerability is already obsolete by the switch to slf4j
  • develop has a lot of infrastructure changes (CircleCI, Gradle update etc.) which would mean additional effort to introduce on master separately for he bug fix.

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.

Copy link
Contributor

@davidlahner davidlahner left a 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.).

@mi-we mi-we changed the title New Version? Merge for version 3.0.0 Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants