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

inherit plugin versions from main pom #2897

Merged
merged 3 commits into from
Sep 11, 2018
Merged

inherit plugin versions from main pom #2897

merged 3 commits into from
Sep 11, 2018

Conversation

olamy
Copy link
Member

@olamy olamy commented Sep 11, 2018

Signed-off-by: olivier lamy oliver.lamy@gmail.com

Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
@olamy olamy added the wip label Sep 11, 2018
pom.xml Outdated
<maven.version>3.5.0</maven.version>
<unix.socket.tmp></unix.socket.tmp>

<!-- some maven plugins versions -->
<surefire.version>2.22.0</surefire.version>
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we make this have the same format of the others, i.e. maven.surefire.plugin.version?

pom.xml Outdated
<maven.resources.plugin.version>3.1.0</maven.resources.plugin.version>
<maven.source.plugin.version>3.0.1</maven.source.plugin.version>
<maven.war.plugin.version>3.2.2</maven.war.plugin.version>
<maven-plugin-tools.version>3.5.2</maven-plugin-tools.version>
Copy link
Contributor

Choose a reason for hiding this comment

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

Ditto, same format as others here?

Copy link
Contributor

Choose a reason for hiding this comment

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

I actually prefer the format maven.plugin.xxx.version so that it's immediate that they are maven plugin related properties.

Copy link
Member Author

Choose a reason for hiding this comment

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

sounds a nice change

<artifactId>it-parent-pom</artifactId>
<version>0.0.1-SNAPSHOT</version>
</parent>

<groupId>org.eclipse.jetty.its.jetty-cdi-run-forked-mojo-it</groupId>
<artifactId>jetty-weld-minimal</artifactId>
<version>1.0-SNAPSHOT</version>
Copy link
Contributor

Choose a reason for hiding this comment

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

The version is not necessary now that there is a parent, I would removed it from all children POMs - less duplication.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't get the need of this one. There is no reason to have parent and child having same version.
Please bear in mind it's ONLY test projects which are not deployed anywhere and versions will NEVER change!
this it parent pom is purely convenient to have common version in all TEST projects. Which is again not mandatory.

Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
@olamy olamy merged commit 1b330f2 into jetty:jetty-9.4.x Sep 11, 2018
@olamy olamy deleted the plugins_versions_as_property branch September 11, 2018 11:05
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.

2 participants