feat!: move vaadin-dev to vaadin-spring-boot-starter

[tltv]

vaadin-dev is moved away from vaadin-core to vaadin-spring-boot-starter.

PartOf: vaadin/flow#22715

[knoobie]

should it also be changed to <optional>true</optional>?

[tltv]

Making it optional here would have same effect as removing it. Which is against the ticket's spec "for Spring Boot projects this won't be a breaking change."
I know it would be beneficial for example for Gradle starters where we wouldn't need to exclude vaadin-dev explicitly then. But
do you have some specific use case in mind where it could be better to either mark it optional here or just remove?

[knoobie]

Hard to say without really testing it.. gonna do that later in the release circle. My current understanding would be that using optional=true would be no breaking change when starting via IDE, otherwise spring devtools would also be missing. But it's just my gut feeling.. nothing tested

[tltv]

I tested this earlier with Spring Boot RC1 (and M3), optional transitive dependency was not included and therefore both vaadin-dev and spring-boot-devtools are now added explicitly as optional dependency in vaadin spring starter apps.
More testing is appreciated so thanks in advance.

[tltv]

Tested this now again with a custom platform snapshot and it's still same. Problem is that optional transitive dependency is not included at all, which means that running via IDE will end up to "DevModeHandlerManager not found" or "missing dev bundle" depending on "frontendHotdeploy" mode.

[knoobie]

Did you also try the following? That's how spring initializr is creating it's pom with 4.0.0-rc.2

    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-devtools</artifactId>
      <scope>runtime</scope>
      <optional>true</optional>
    </dependency>

[tltv]

not yet. I'll give it a try.

[tltv]

runtime scope didn't change anything in this context.

[knoobie]

Damn.. that's sad.. thanks for checking!