-
Notifications
You must be signed in to change notification settings - Fork 190
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
NO-ISSUE: Maven plugins update #2819
Changes from all commits
a1422c7
15999bd
47dd0a8
3355855
f5c5e2b
e904646
6ebc956
8a18eaf
58020e7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -187,29 +187,29 @@ | |
<version.antrun.plugin>1.8</version.antrun.plugin> | ||
<version.buildhelper.plugin>3.0.0</version.buildhelper.plugin> | ||
<version.bundle.plugin>3.3.0</version.bundle.plugin> | ||
<version.checkstyle.plugin>3.2.0</version.checkstyle.plugin> | ||
<version.clean.plugin>3.1.0</version.clean.plugin> | ||
<version.compiler.plugin>3.12.1</version.compiler.plugin> | ||
<version.dependency.plugin>3.3.0</version.dependency.plugin> | ||
<version.deploy.plugin>2.8.2</version.deploy.plugin> | ||
<version.enforcer.plugin>3.1.0</version.enforcer.plugin> | ||
<version.checkstyle.plugin>3.4.0</version.checkstyle.plugin> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is expected dashbuilder overrides to 3.1.1? I think preferred would be single version everywhere if possible There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I purposely didn't touch dashbuilder because is not a project under our control, however, I can do a tentative There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jomarko Updated versions in |
||
<version.clean.plugin>3.4.0</version.clean.plugin> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same comment as above |
||
<version.compiler.plugin>3.13.0</version.compiler.plugin> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same comment as above |
||
<version.dependency.plugin>3.7.1</version.dependency.plugin> | ||
<version.deploy.plugin>3.1.2</version.deploy.plugin> | ||
<version.enforcer.plugin>3.5.0</version.enforcer.plugin> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same comment as above |
||
<version.failsafe.plugin>${version.surefire.plugin}</version.failsafe.plugin> | ||
<version.install.plugin>2.5.2</version.install.plugin> | ||
<version.install.plugin>3.1.2</version.install.plugin> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same comment as above There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. version misalignment is also for:
|
||
<version.jacoco.plugin>0.8.11</version.jacoco.plugin> | ||
<version.jar.plugin>3.1.0</version.jar.plugin> | ||
<version.jarjar.plugin>1.5</version.jarjar.plugin> | ||
<version.org.jvnet.jaxb2.maven2.maven-jaxb2-plugin>0.15.1</version.org.jvnet.jaxb2.maven2.maven-jaxb2-plugin> | ||
<version.org.kie.gwthelper.maven>1.3</version.org.kie.gwthelper.maven> | ||
<version.org.kogito.gwt-jsonix-schema-compiler>1.3.0</version.org.kogito.gwt-jsonix-schema-compiler> | ||
<version.replacer.plugin>1.5.2</version.replacer.plugin> | ||
<version.resources.plugin>3.2.0</version.resources.plugin> | ||
<version.shade.plugin>3.2.1</version.shade.plugin> | ||
<version.site.plugin>3.7.1</version.site.plugin> | ||
<version.resources.plugin>3.3.1</version.resources.plugin> | ||
<version.shade.plugin>3.6.0</version.shade.plugin> | ||
<version.site.plugin>3.12.1</version.site.plugin> | ||
<version.spotbugs-maven-plugin>3.1.8</version.spotbugs-maven-plugin> | ||
<version.sonar.plugin>3.9.1.2184</version.sonar.plugin> | ||
<version.source.plugin>3.3.1</version.source.plugin> | ||
<version.surefire.plugin>3.2.5</version.surefire.plugin> | ||
<version.war.plugin>3.2.2</version.war.plugin> | ||
<version.surefire.plugin>3.3.0</version.surefire.plugin> | ||
<version.war.plugin>3.4.0</version.war.plugin> | ||
<version.zanata.plugin>2.3.0</version.zanata.plugin> | ||
|
||
<!-- Third party Libraries --> | ||
|
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.
hm, this sounds a little bit non-standard to me, is that intentional to combine failsafe and surefire versions? furthermore version.maven.failsafe.plugin seems to be unused
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.
@jomarko Yes, that's correct. failsafe and surefire have the same release cycle. apache pom manages that in the same way: https://repo.maven.apache.org/maven2/org/apache/apache/32/apache-32.pom