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

Correct typo in artifactId of dependency in bom pom.xml #6989

Closed
wants to merge 1 commit into from

Conversation

normanmaurer
Copy link
Member

@normanmaurer normanmaurer commented Jul 18, 2017

Motivation:

There was a typo in a dependency in the bom pom.xml which lead to have it specify a non-existing artifact and also so not have the maven release plugin update the version correctly.

Modifications:

Rename netty-transport-unix-common to netty-transport-native-unix-common and also fix the version.

Result:

Fixes [#6979]

@normanmaurer
Copy link
Member Author

@tsachev and @wilkinsona PTAL ... This should fix [#6979]

Copy link
Member

@Scottmitch Scottmitch left a comment

Choose a reason for hiding this comment

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

lgtm

@Scottmitch
Copy link
Member

I thought we had this at one point though ... and there was something with the release process that prevented using the variable? I may be confusing some other issue though...

@wilkinsona
Copy link
Contributor

That was my concern too. It looks fine in terms of using the variable consistently, but I don't know anything about Netty's release process so I also don't know if it'll work as intended.

@normanmaurer
Copy link
Member Author

@Scottmitch @wilkinsona the problem is that if we use the version directly the maven release plugin will NOT update the version for the dependencies that also have the classifier listed. So I think this is the way to go and also "consistent" with how we add the dependencies in the all module.

@tsachev
Copy link

tsachev commented Jul 19, 2017

I do not have an opinion on using project.version (unless it makes the bom useless as parent, but that is not its purpose anyway).
There might be something in the release process that replaces ${project.version} with the actual project version I don't know.

But #6979 is about using wrong artifactId which manifests itself in the bom, because maven-release-plugin does not see this non existing module and fails to update them.

<artifactId>netty-transport-unix-common</artifactId> should become <artifactId>netty-transport-native-unix-common</artifactId> everywhere. Note the missing native in the name.

@normanmaurer
Copy link
Member Author

@tsachev doh! I missed this ... so I think this is the real issue then.. Let me update the pr to just fix the artifactId, this should be good enough.

Motivation:

There was a typo in a dependency in the bom pom.xml which lead to have it specify a non-existing artifact and also so not have the maven release plugin update the version correctly.

Modifications:

Rename netty-transport-unix-common to netty-transport-native-unix-common and also fix the version.

Result:

Fixes [#6979]
@normanmaurer normanmaurer changed the title Use project.version property to specify the version of the dependenci… Correct typo in artifactId of dependency in bom pom.xml Jul 19, 2017
@normanmaurer
Copy link
Member Author

@Scottmitch @wilkinsona @tsachev PTAL again

@wilkinsona
Copy link
Contributor

LGTM

@normanmaurer
Copy link
Member Author

Cherry-picked into 4.1 (deb5c45) and committed a updated version to 4.0 (ae66f3a)

@normanmaurer normanmaurer deleted the bom_fix branch July 19, 2017 12:27
@Scottmitch
Copy link
Member

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants