-
Notifications
You must be signed in to change notification settings - Fork 70
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
[AMLII-1828] Cleaning up pom.xml #529
Conversation
5fa6ad9
to
ba7b648
Compare
3c45d29
to
171f467
Compare
7d1968c
to
311e4a6
Compare
750e9c1
to
83b5134
Compare
@@ -95,7 +100,7 @@ | |||
<plugin> | |||
<groupId>org.sonatype.plugins</groupId> | |||
<artifactId>nexus-staging-maven-plugin</artifactId> | |||
<version>1.6.13</version> | |||
<version>${nexus-staging-maven-plugin.version}</version> |
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.
Just curious, what is the advantage of specifying the version via a property?
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.
I went back and forth between specifying them in property or just moving them out of property completely or moving it all to dependency-management
section. I was aiming for some consistency while I went through and upgraded some of the plugins and dependencies as we had mixture.
Cleaned up the
pom.xml
and bumped some of the dependencies. Deployments still work after all the changes (seeSNAPSHOT
here).