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

FLUME-3093: Groundwork for version changes in root pom #132

Closed
wants to merge 5 commits into from

Conversation

mcsanady
Copy link
Contributor

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

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
@mcsanady
Copy link
Contributor Author

Tested with mvn dependency:tree : no difference detected.

Copy link
Contributor Author

@mcsanady mcsanady left a 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

@mcsanady mcsanady closed this Jun 29, 2017
@mcsanady mcsanady deleted the FLUME-3093 branch June 29, 2017 15:46
@mcsanady mcsanady restored the FLUME-3093 branch June 29, 2017 15:46
@mcsanady
Copy link
Contributor Author

I accidentally deleted the branch

@mcsanady mcsanady reopened this Jun 29, 2017
@@ -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>
Copy link
Contributor

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>
Copy link
Contributor

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

@@ -147,7 +147,7 @@
<dependency>
<groupId>com.github.stefanbirkner</groupId>
<artifactId>system-rules</artifactId>
<version>1.16.0</version>
<version>${system-rules.version}</version>
Copy link
Contributor

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>

Copy link
Contributor

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

@simonati
Copy link

Hi @mcsanady,
I think this is a neat idea I would like to finish my review soon.

@asfgit asfgit closed this in 63aabc4 Aug 7, 2017
@mcsanady mcsanady deleted the FLUME-3093 branch September 11, 2017 10:06
mcsanady pushed a commit to mcsanady/flume that referenced this pull request Mar 13, 2018
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
waidr pushed a commit to waidr/flume that referenced this pull request Jul 24, 2019
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.

None yet

3 participants