Skip to content

Conversation

@RobertAvemarg
Copy link
Contributor

  • updated allure-cucumber6-jvm to allure-cucumber7-jvm to fix the incompatibility problem
  • added IntelliJ project directory to gitignore
  • already incremented the Neodymium version

@oomelianchuk oomelianchuk linked an issue Dec 13, 2024 that may be closed by this pull request
@oomelianchuk oomelianchuk force-pushed the #319_update_Allure_Cucumber_jvm branch from 8584865 to e759fb7 Compare December 18, 2024 10:08
<groupId>com.xceptance</groupId>
<artifactId>neodymium-library</artifactId>
<version>5.1.1</version>
<version>5.1.2</version>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just as a node: don't change the version number in the pom to the planned release one. If every tickets updates this line, we'll have a merge conflict, if the ticket is postponed, we might overlook this and merge a wrong version into develop

@wurzelkuchen wurzelkuchen merged commit e7e0c28 into develop Jan 22, 2025
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.

Cucumber version not compatible with the Allure Cucumber jvm

4 participants