Closed beckerjohannes closed 3 years ago
As long as the new version is not released, you can upgrade the used generator in your own pom.xml:
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.assertj</groupId>
<artifactId>assertj-assertions-generator-maven-plugin</artifactId>
<version>2.1.0</version>
<dependencies>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-assertions-generator</artifactId>
<version>2.2.1</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</pluginManagement>
</build>
When I do that, I get the following error:
[ERROR] Failed to execute goal org.assertj:assertj-assertions-generator-maven-plugin:2.2.0:generate-assertions (default) on project ecamp-server: Execution default of goal org.assertj:assertj-assertions-generator-maven-plugin:2.2.0:generate-assertions failed: Plugin org.assertj:assertj-assertions-generator-maven-plugin:2.2.0 or one of its dependencies could not be resolved: Failed to collect dependencies for org.assertj:assertj-assertions-generator-maven-plugin:jar:2.2.0 (): Could not resolve version conflict among [org.assertj:assertj-assertions-generator-maven-plugin:jar:2.2.0 -> org.assertj:assertj-assertions-generator:jar:2.2.1 -> org.assertj:assertj-core:jar:[3.15.0,3.99.0], org.assertj:assertj-assertions-generator-maven-plugin:jar:2.2.0 -> org.assertj:assertj-core:jar:[2.0.0,2.99.0]]
@beckerjohannes I don't have such issue after adding an explicit dependency as mentioned by @nickstolwijk. FYI I also have specified the assertj-core version explicitly. see https://github.com/assertj/assertj-examples/commit/107f76eed474c31aad49f6db1b2ee459d1117206
@joel-costigliola explicitly specifying the assertj-core version does the trick. THX
Can you please cut a new release that depends on the newly released 2.2.1 version of the
assertj-assertions-generator