-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
FLUME-3093: Groundwork for version changes in root pom #132
Conversation
Extracted hard-coded version numbers to root pom.xml No version number changed in this step. The old used versions are named with -old suffix. guava-old.version httpclient-old.version mvn-surefire-plugin-old.version mvn-surefire-plugin-old-morphline.version
Tested with mvn dependency:tree : no difference detected. |
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.
Removed unnecessary flume.version variable.
Testing: mvn dependency:tree outputs are identical
I accidentally deleted the branch |
flume-ng-auth/pom.xml
Outdated
@@ -37,7 +37,7 @@ limitations under the License. | |||
<plugin> | |||
<groupId>org.apache.felix</groupId> | |||
<artifactId>maven-bundle-plugin</artifactId> | |||
<version>2.3.7</version> | |||
<version>${bundle-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.
why don't we use <pluginManagement>
in the parent pom?
@@ -86,14 +86,14 @@ | |||
<dependency> | |||
<groupId>org.mockito</groupId> | |||
<artifactId>mockito-all</artifactId> | |||
<version>1.9.0</version> | |||
<version>${mockito.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.
Why don't we use <dependencyManagement>
in the parent pom
flume-ng-node/pom.xml
Outdated
@@ -147,7 +147,7 @@ | |||
<dependency> | |||
<groupId>com.github.stefanbirkner</groupId> | |||
<artifactId>system-rules</artifactId> | |||
<version>1.16.0</version> | |||
<version>${system-rules.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.
dependencyManagement?
<wiremock.version>1.53</wiremock.version> | ||
<guava.version>18.0</guava.version> | ||
</properties> | ||
|
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.
Now, that we use common versions, we might would like to look at the exlusions in the dependencies. Again, the version numbers could come from dependencyManagement
Hi @mcsanady, |
This commit extracts the version numbers from the subprojects' pom.xml to the root pom.xml without introducing any other change (i.e. the dependency tree didn't change) This closes apache#132 Reviewers: Ferenc Szabo, Attila Simon (Miklos Csanady via Denes Arvay) Change-Id: Ib3aaf685c2b6bc72242415d9204d1c282d4be372
Extracted hard-coded version numbers to root pom.xml
No version number changed in this step. The old used versions are named with -old suffix.
guava-old.version
httpclient-old.version
mvn-surefire-plugin-old.version
mvn-surefire-plugin-old-morphline.version