Skip to content

Conversation

@jkschneider
Copy link
Contributor

Proposed solution for #12676.

HierarchicalNameMapper is not a component that can be shared amongst multiple monitoring systems.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 29, 2018
@snicoll
Copy link
Member

snicoll commented Mar 29, 2018

Thanks @jkschneider, this is what I had in mind. It's a breaking change in the sense that a custom HierarchicalNameMapper bean wouldn't be taken into account anymore.

Given that doing that is wrong, I am in favour of merging this. Let's see what the rest of the team thinks.

@philwebb
Copy link
Member

I think we should merge this, probably better to make a small breaking change than limp on with a bad assumption.

@philwebb philwebb added this to the 2.0.x milestone Mar 29, 2018
@philwebb philwebb added type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 29, 2018
@snicoll snicoll removed the for: team-attention An issue we'd like other members of the team to review label Mar 29, 2018
@snicoll snicoll modified the milestones: 2.0.x, 2.0.1 Apr 3, 2018
snicoll pushed a commit that referenced this pull request Apr 3, 2018
HierarchicalNameMapper is not a component that can be shared amongst
multiple monitoring systems.

See gh-12683
@snicoll snicoll closed this in 7dbeaaa Apr 3, 2018
snicoll added a commit that referenced this pull request Apr 3, 2018
* pr/12683:
  Polish "Remove HierarchicalNameMapper as a configured @bean"
  Remove HierarchicalNameMapper as a configured @bean
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.

4 participants