rangeStart - unlogical outcome

I have

import com.vaadin.ui.DateField;
import java.time.LocalDate;

and do

DateField out = new DateField("Some title");
Date input = new Date();
LocalDate date = input.toInstant().atZone(ZoneId.systemDefault()).toLocalDate();
out.setValue(date);

for this I get

java.lang.NoSuchFieldError: rangeStart
	at com.vaadin.ui.AbstractDateField.getRangeStart(AbstractDateField.java:349)
	at com.vaadin.ui.AbstractLocalDateField.getRangeValidator(AbstractLocalDateField.java:101)
	at com.vaadin.ui.AbstractDateField.doSetValue(AbstractDateField.java:699)
	at com.vaadin.ui.AbstractDateField.doSetValue(AbstractDateField.java:74)
	at com.vaadin.ui.AbstractField.setValue(AbstractField.java:140)
	at com.vaadin.ui.AbstractField.setValue(AbstractField.java:53)
	at com.vaadin.ui.AbstractDateField.setValue(AbstractDateField.java:545)

The implementation of getRangeStart is

public T getRangeStart() {
    return convertFromDateString(getState(false).rangeStart);
}

And the implementation of getState(boolean) is

@Override
protected AbstractDateFieldState getState(boolean markAsDirty) {
    return (AbstractDateFieldState) super.getState(markAsDirty);
}

It is running in Tomcat with OpenJDK 11. The code comes from the jar-file vaadin-shared-8.8.2.jar with md5 91eb80e41934a8751d9ca588ceb3a8d7 and has beed inspected by navigation with Eclipse IDE.

Sinse AbstractDateFieldState had the field rangeStart from the beginning (I believe) this should not happen. The alternatives are a null pointer error or the cast in getState should fail.

I cannot find anything on the net about similar experiences. Any help greatly appreciated.

First the stack trace when faulting

sep 17 15:41:54 prvcosv01.prv.se java[11964]

: 2019-09-17 15:41:54.327 ERROR 11964 — [nio-8116-exec-7]
com.vaadin.server.DefaultErrorHandler :
sep 17 15:41:54 prvcosv01.prv.se java[11964]
: java.lang.NoSuchFieldError: rangeStart
sep 17 15:41:54 prvcosv01.prv.se java[11964]
: at com.vaadin.ui.AbstractDateField.getRangeStart(AbstractDateField.java:349) ~[vaadin-server-8.2.0.jar!/:8.2.0]

sep 17 15:41:54 prvcosv01.prv.se java[11964]

: at com.vaadin.ui.AbstractLocalDateField.getRangeValidator(AbstractLocalDateField.java:101) ~[vaadin-server-8.2.

Here is some output from mvn dependency:tree

[INFO]

| ± com.vaadin:vaadin-spring:jar:3.1.1:compile
[INFO]
| | ± org.springframework:spring-web:jar:4.3.9.RELEASE:compile
[INFO]
| | | ± org.springframework:spring-aop:jar:4.3.9.RELEASE:compile
[INFO]
| | | ± org.springframework:spring-beans:jar:4.3.9.RELEASE:compile
[INFO]
| | | ± org.springframework:spring-context:jar:4.3.9.RELEASE:compile
[INFO]
| | | - org.springframework:spring-core:jar:4.3.9.RELEASE:compile
[INFO]
| | ± com.vaadin:vaadin-server:jar:8.2.0:compile

The problem is in vaadin-server so I upgrade vaadin-spring to 3.2.1 and then get vaadin-server 8.8.0 and then the problem is solved. There must be a faulty dependency behind this.