Spring-cloud-netflix: Rename starters to include `-netflix-`

Created on 23 Nov 2015  路  21Comments  路  Source: spring-cloud/spring-cloud-netflix

All the starters in the other projects include more context.

spring-cloud-starter-consul-discovery, or spring-cloud-starter-zookeeper-config.

I would only do this post Brixton, in the C release train.

enhancement

Most helpful comment

spring-cloud-starter-openfeign looks good to me as it reflect the actual project name. If you google around feign alone then you will be directed to the former Netflix stuff...

My 2 cents...

All 21 comments

Add the new starters in Dalston, remove old starters in Edgware

I've started working on this issue. I'm having second though on spring-cloud-starter-eureka. When I started on Spring Cloud, I remember getting confused between spring-cloud-starter-eureka and spring-cloud-starter-eureka-server.

How about renaming the client to spring-cloud-starter-netflix-eureka-client ? I know it's getting long... but we can't escape thespring-cloud-starter-netflix-eureka-server.

@daniellavoie, yeah that makes sense.

Adjustment coming through ;) Made a first PR with the old name.

NP

@philwebb what does boot do when they rename/deprecate a starter? It would be nice to print a warning that the user is using a deprecated starter.

Nice, so you do log a warning. Thanks @philwebb

Just pushed a new version with the shiny spring-cloud-starter-netflix-eureka-client

@daniellavoie, feign shouldn't be spring-cloud-starter-netflix-feign since it's not netflix anymore. Either keep it spring-cloud-starter-feign or spring-cloud-starter-openfeign. What do you think @adriancole.

@spencergibb I understand your point but given this logic, feign should not be part of the spring-cloud-netflix project anymore then. Still, I'll rename it once @adriancole provides us his preference.

spring-cloud-starter-openfeign looks good to me as it reflect the actual project name. If you google around feign alone then you will be directed to the former Netflix stuff...

My 2 cents...

@daniellavoie yup, it should move out of netflix. Maybe during 2.0.0.

I like spring-cloud-starter-openfeign

What's the next next train after Edgware ? I'll deprecate the old starters with a new issue / PR.

Finchley

@daniellavoie so it would be nice to have the deprecations in Edgware so they can be removed in Finchley.

Re-opening. If we are deprecating in 1.4.0, shouldn't we remove in 2.0.0? Also, the turbine-amqp starter can probably be retired in 1.4.0 (it was only kept for backwards compatibility). I'm also not convinced we need the hystrix-dashboard starter.

yes, we should remove them. Nice catch on jar vs pom packaging.

@spencergibb @dsyer I think we should close this issue and open a separate issue for removing the starters in 2.0.0. This issue was focused on renaming them in Edgware. I think it will be cleaner if we have a separate issue for Finchley that removes them.

Closing this issue, opened separate issues for the starters that need to be removed.

Was this page helpful?
0 / 5 - 0 ratings