See: spring-projects/spring-tools#313

Summary:

When we create a project with initializer and select both 'cloud-function' and 'webflux' dependencies, then a pom with these dependencies is created:

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-webflux</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-function-web</artifactId>
		</dependency>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-test</artifactId>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>io.projectreactor</groupId>
			<artifactId>reactor-test</artifactId>
			<scope>test</scope>
		</dependency>
	</dependencies>

According to the metadata returned from this end-point:

https://start-development.cfapps.io/dependencies?bootVersion=2.1.6.RELEASE

The starter with id 'cloud-function' corresponds to a maven dependency with gid:aid of: org.springframework.cloud:spring-cloud-function-context. That dependency is not present in the pom unfortunately.

THe upshot of this is that STS Edit Starters functionality gets confused about which starters are selected in this pom. (There is no way for STS to know that org.springframework.cloud:spring-cloud-function-web represents the 'cloud-function' starter dependency). This makes the Edit Starters wizard behave incorrectly whenever a pom contains that element.