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

Dependency management for micrometer-registry-cloudwatch is missing #13982

Closed

Conversation

cmakinen
Copy link
Contributor

@cmakinen cmakinen commented Aug 2, 2018

Added micrometer-registry-cloudwatch to spring-boot dependencyManagement section.

Refers to issue: #13981

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 2, 2018
@snicoll
Copy link
Member

snicoll commented Aug 2, 2018

@cmakinen thanks for the PR but before we add this to the dependency management, I'd like to understand why we don't have auto-configuration at all for this (in the current state adding the version in the two other modules is useless).

paging @jkschneider

@snicoll snicoll added the status: waiting-for-feedback We need additional information before we can continue label Aug 2, 2018
@spencergibb
Copy link
Member

It is in spring cloud aws

@snicoll
Copy link
Member

snicoll commented Aug 2, 2018

Thanks Spencer, some more info in this comment.

@cmakinen can you please rework your PR to remove the inclusion of that library in the autoconfigure and docs modules?

@snicoll snicoll changed the title Bringing in micrometer-registry-cloudwatch Add dependency management for micrometer-registry-cloudwatch Aug 2, 2018
@snicoll snicoll self-assigned this Aug 2, 2018
@snicoll snicoll added type: bug A general bug and removed status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Aug 2, 2018
@snicoll snicoll added this to the 2.0.5 milestone Aug 2, 2018
snicoll added a commit that referenced this pull request Aug 2, 2018
* pr/13982:
  Add dependency management for micrometer-registry-cloudwatch
@snicoll snicoll closed this in 07d9668 Aug 2, 2018
@snicoll
Copy link
Member

snicoll commented Aug 2, 2018

@cmakinen thank you very much for your first contribution to Spring Boot. This has been merged in 2.0.x and master.

@cmakinen
Copy link
Contributor Author

cmakinen commented Aug 2, 2018

Thanks @snicoll Really appreciate it!! Happy to contribute :)

@jkschneider
Copy link
Contributor

If we dependency manage micrometer-registry-cloudwatch in Spring Boot, we are effectively dependency managing the AWS SDK which iterates quite a bit faster than Spring Boot.

That’s why we left this to spring-cloud-aws.

@snicoll
Copy link
Member

snicoll commented Aug 2, 2018

Reopening to double check we didn’t do this on purpose

@snicoll snicoll reopened this Aug 2, 2018
@snicoll snicoll added the for: team-attention An issue we'd like other members of the team to review label Aug 2, 2018
@wilkinsona
Copy link
Member

If we dependency manage micrometer-registry-cloudwatch in Spring Boot, we are effectively dependency managing the AWS SDK

I don't think we are. The dependency management of micrometer-registry-cloudwatch will have no direct effect on the version of the AWS SDK. The version of the AWS SDK would only be affected if the user adds a dependency on micrometer-registry-cloudwatch and then, in the absence of any other dependency on the AWS SDK, they'll get whatever version of the AWS SDK is pulled in transitively. In terms of the version of the AWS SDK, this is no different to the user manually specifying the version of micrometer-registry-cloudwatch.

@wilkinsona wilkinsona changed the title Add dependency management for micrometer-registry-cloudwatch Dependency management for micrometer-registry-cloudwatch is missing Aug 6, 2018
@wilkinsona wilkinsona removed the for: team-attention An issue we'd like other members of the team to review label Aug 6, 2018
@wilkinsona wilkinsona closed this Aug 6, 2018
@jkschneider
Copy link
Contributor

Thanks @wilkinsona. My (incorrect) assumption was that you were using some automation to generate the Spring Boot BOM to form the transitive closure of first-order dependencies of Spring Boot.

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

Successfully merging this pull request may close these issues.

None yet

6 participants