Update a Vaadin 10 project to Vaadin 11 beta?

Martin595 · November 8, 2018, 3:27am

Hi Basil,

For Maven, use the URL from the POM example above

        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

        <repository>
            <id>vaadin-addons</id>
            <url>http://maven.vaadin.com/vaadin-addons</url>
        </repository>

Basil3 · November 8, 2018, 4:34am

Martin Israelsen:
Hi Basil,

For Maven, use the URL from the POM example above

        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

Nope. As I said above, that URL leads to [an XML file]
(https://maven.vaadin.com/vaadin-prereleases/archetype-catalog.xml) that contains data for Vaadin 7 & 8, but not 10 and later.

Basil3 · November 8, 2018, 4:41am

Martin Israelsen:
Hi Basil,

For Maven, use the URL from the POM example above

        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

Nope. As I said above, that URL leads to [an XML file]
(https://maven.vaadin.com/vaadin-prereleases/archetype-catalog.xml) that contains data for Vaadin 7 & 8, but not 10 and later.

So this POM:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns = "http://maven.apache.org/POM/4.0.0"
         xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation = "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.basilbourque.acmekit</groupId>
    <artifactId>acmekit</artifactId>
    <name>Bogus</name>
    <version>1.0-SNAPSHOT</version>
    <packaging>war</packaging>

    <properties>
        <maven.compiler.source>10</maven.compiler.source>
        <maven.compiler.target>10</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <failOnMissingWebXml>false</failOnMissingWebXml>

        <!--<vaadin.version>11.0.1</vaadin.version>-->
        <vaadin.version>12.0.0alpha5</vaadin.version>
    </properties>

    <repositories>
        <!-- Repository used by many Vaadin add-ons -->
        <repository>
            <id>Vaadin Directory</id>
            <url>http://maven.vaadin.com/vaadin-addons</url>
        </repository>

        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

    </repositories>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-bom</artifactId>
                <type>pom</type>
                <scope>import</scope>
                <version>${vaadin.version}</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-core</artifactId>
        </dependency>

        <!-- Added to provide logging output as Flow uses -->
        <!-- the unbound SLF4J no-operation (NOP) logger implementation -->
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
        </dependency>

        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.1.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <!-- Jetty plugin for easy testing without a server -->
            <plugin>
                <groupId>org.eclipse.jetty</groupId>
                <artifactId>jetty-maven-plugin</artifactId>
                <version>9.4.11.v20180605</version>
                <configuration>
                    <scanIntervalSeconds>1</scanIntervalSeconds>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <profiles>
        <profile>
            <!-- Production mode can be activated with either property or profile -->
            <id>production-mode</id>
            <activation>
                <property>
                    <name>vaadin.productionMode</name>
                </property>
            </activation>
            <properties>
                <vaadin.productionMode>true</vaadin.productionMode>
            </properties>

            <dependencies>
                <dependency>
                    <groupId>com.vaadin</groupId>
                    <artifactId>flow-server-production-mode</artifactId>
                </dependency>
            </dependencies>

            <build>
                <plugins>
                    <plugin>
                        <groupId>com.vaadin</groupId>
                        <artifactId>vaadin-maven-plugin</artifactId>
                        <version>${vaadin.version}</version>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>copy-production-files</goal>
                                    <goal>package-for-production</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>

… when doing a Maven clean results in this error:

/Library/Java/JavaVirtualMachines/zulu-10.jdk/Contents/Home/bin/java -Dmaven.multiModuleProjectDirectory=/Users/basilbourque/IdeaProjects/AcmeKit -Dmaven.home=/Users/basilbourque/Documents/Tools/Maven/apache-maven-3.5.4 -Dclassworlds.conf=/Users/basilbourque/Documents/Tools/Maven/apache-maven-3.5.4/bin/m2.conf "-javaagent:/Applications/IntelliJ IDEA 2018.3 EAP.app/Contents/lib/idea_rt.jar=65077:/Applications/IntelliJ IDEA 2018.3 EAP.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath /Users/basilbourque/Documents/Tools/Maven/apache-maven-3.5.4/boot/plexus-classworlds-2.5.2.jar org.codehaus.classworlds.Launcher -Didea.version=2018.3 clean
[INFO]
 Scanning for projects...
[ERROR]
 [ERROR]
 Some problems were encountered while processing the POMs:
[ERROR]
 Non-resolvable import POM: Failure to find com.vaadin:vaadin-bom:pom:12.0.0alpha5 in http://maven.vaadin.com/vaadin-addons was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin Directory has elapsed or updates are forced @ line 35, column 21
[ERROR]
 'dependencies.dependency.version' for com.vaadin:vaadin-core:jar is missing. @ line 46, column 17
[ERROR]
 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ line 53, column 17
 @ 
[ERROR]
 The build could not read 1 project -> [Help 1]

[ERROR]
   
[ERROR]
   The project com.basilbourque.acmekit:acmekit:1.0-SNAPSHOT (/Users/basilbourque/IdeaProjects/AcmeKit/pom.xml) has 3 errors
[ERROR]
     Non-resolvable import POM: Failure to find com.vaadin:vaadin-bom:pom:12.0.0alpha5 in http://maven.vaadin.com/vaadin-addons was cached in the local repository, resolution will not be reattempted until the update interval of Vaadin Directory has elapsed or updates are forced @ line 35, column 21 -> [Help 2]

[ERROR]
     'dependencies.dependency.version' for com.vaadin:vaadin-core:jar is missing. @ line 46, column 17
[ERROR]
     'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ line 53, column 17
[ERROR]
 
[ERROR]
 To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR]
 Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
 
[ERROR]
 For more information about the errors and possible solutions, please read the following articles:
[ERROR]
 [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR]
 [Help 2]
 http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Process finished with exit code 1

Martin595 · November 8, 2018, 5:23am

Hi Basil,

Not quite sure what is causing that error. I’m using the same repository settings that you have in your example and I tried switching to 12.0.0.alpha5, and it compiled just fine here, both on command line and in Eclipse.

Zhe3 · November 8, 2018, 7:32am

Hi Basil, I just noticed one thing that, the version you used is <vaadin.version>12.0.0alpha5</vaadin.version> which is not correct… because it should be 12.0.0.alpha5 and you are missing a dot. By the way, the 12.0.0.beta1 has been released recently. so you can also try that.

Basil3 · November 8, 2018, 8:29pm

Zhe Sun:
…By the way, the 12.0.0.beta1 has been released recently. so you can also try that.

➥ How do you know what versions have been released?

I can find no such listing for Vaadin Flow. My only indication has been the version displayed in the JavaDoc:

https://vaadin.com/api/platform/12.0.0.alpha5/overview-summary.html

…which currently is still at alpha5.

Basil3 · November 8, 2018, 9:36pm

Close but no cigar.

After doing these steps:

(1) Add this element to the <repositories> element:

<repository>
    <id>vaadin-prereleases</id>
    <url>https://maven.vaadin.com/vaadin-prereleases</url>
</repository>

(2) Change this element:

<vaadin.version>11.0.1</vaadin.version>

…to this element:

<vaadin.version>12.0.0.beta1</vaadin.version>

(3) Run a Maven clean.

(4) Run a Maven install.

… I do get Vaadin 12 beta 1, and the app actually runs, but my POM now reports an error:

Plugin 'com.vaadin:vaadin-maven-plugin:12.0.0.beta1' not found

In the attachment screenshot, notice (a) the vaadin-core library is updated to 12.0.0.beta1 successfully, and (b) error message floating over the <version>${vaadin.version}</version> element.

Pekka3 · November 9, 2018, 8:09am

Hello Basil. One of the easiest ways of seeing what is released is to subscribe to the github release notes for the platform https://github.com/vaadin/platform/releases. The javadocs for V12 beta1 will be online on the website soon.

The issue you’re having is that you’re missing the <pluginRepository> from your pom.xml. You need to add the vaadin-prereleases repository there too, as for some reason those are defined separately in Maven.

    <pluginRepositories>
        <!-- Repository needed for prerelease versions of Vaadin -->
        <pluginRepository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </pluginRepository>
    </pluginRepositories>

I recommend that whenever you’re in doubt about what should be in the pom.xml or when you’re starting a new project, you take one of the project bases from the vaadin.com/start to get everything setup like it should, or you can use those as examples for your project to see what you might be missing. All the free starters are also available on github: https://github.com/vaadin/skeleton-starter-flow/blob/master/pom.xml

Basil3 · November 10, 2018, 4:39am

Pekka Hyvönen:
…when you’re starting a new project, you take one of the project bases from the vaadin.com/start to get everything setup like it should,

That is indeed just what I did, with no problem.

The problem is in trying to modify that given starter project to use the alpha/beta versions. I have yet to use the alpha/beta successfully. As shown in my previous message above, I can run 12.0.0.beta1 but with a POM error: Plugin 'com.vaadin:vaadin-maven-plugin:12.0.0.beta1' not found

Pekka3 · November 10, 2018, 2:56pm

Did you try adding the pluginRepository (see my previous post)? The error comes from not having the prerelease repository for the plugin defined in pom.xml.

Basil3 · November 11, 2018, 3:31am

Pekka Hyvönen:
Did you try adding the pluginRepository (see my previous post)? The error comes from not having the prerelease repository for the plugin defined in pom.xml.

Yes, I did.

Here is a brand-new fresh project created today using the [Project Base]
(https://vaadin.com/start/latest/project-base) starter pack.

I made 3 changes to the pom.xml file.

(1) I changed the content of the vaadin.version element.

    <!--<vaadin.version>11.0.0</vaadin.version>-->
    <!--change-this-for-alphabetas-->
    <vaadin.version>12.0.0.beta1</vaadin.version>

(2) I added this repository element to the repositories element.

    <!--add-this-for-alphabetas-->
    <repository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </repository>

(3) I added the pluginRepositories element with sub-element pluginRepository to the project element.

<!--add-this-for-alphabetas-->
<pluginRepositories>
    <!-- Repository needed for prerelease versions of Vaadin -->
    <pluginRepository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </pluginRepository>
</pluginRepositories>

After doing the IntelliJ menu item Build > Rebuild Project, and then doing a Maven clean from within IntelliJ, I get an error in the Maven pom.xml file:

Plugin ‘com.vaadin:vaadin-maven-plugin:12.0.0.beta1’ not found

Error occurs for line # 120 seen below:

<version>${vaadin.version}</version>

Here is the entire POM. You can find my changes by searching for the word alphabetas. All 3 changes are in the top-half of the file.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns = "http://maven.apache.org/POM/4.0.0"
         xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation = "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.basilbourque.example</groupId>
    <artifactId>alphabeta</artifactId>
    <name>AlphaBeta</name>
    <version>1.0-SNAPSHOT</version>
    <packaging>war</packaging>

    <properties>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <failOnMissingWebXml>false</failOnMissingWebXml>

        <!--<vaadin.version>11.0.0</vaadin.version>-->
        <!--change-this-for-alphabetas-->
        <vaadin.version>12.0.0.beta1</vaadin.version>
        <!--  To discover the latest pre-release, see: https://github.com/vaadin/platform/releases  -->
    </properties>

    <repositories>
        <!-- Repository used by many Vaadin add-ons -->
        <repository>
            <id>Vaadin Directory</id>
            <url>http://maven.vaadin.com/vaadin-addons</url>
        </repository>

        <!--add-this-for-alphabetas-->
        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

    </repositories>

    <!--add-this-for-alphabetas-->
    <pluginRepositories>
        <!-- Repository needed for prerelease versions of Vaadin -->
        <pluginRepository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </pluginRepository>
    </pluginRepositories>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-bom</artifactId>
                <type>pom</type>
                <scope>import</scope>
                <version>${vaadin.version}</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-core</artifactId>
        </dependency>

        <!-- Added to provide logging output as Flow uses -->
        <!-- the unbound SLF4J no-operation (NOP) logger implementation -->
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
        </dependency>

        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.1.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <!-- Jetty plugin for easy testing without a server -->
            <plugin>
                <groupId>org.eclipse.jetty</groupId>
                <artifactId>jetty-maven-plugin</artifactId>
                <version>9.4.11.v20180605</version>
                <configuration>
                    <scanIntervalSeconds>1</scanIntervalSeconds>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <profiles>
        <profile>
            <!-- Production mode can be activated with either property or profile -->
            <id>production-mode</id>
            <activation>
                <property>
                    <name>vaadin.productionMode</name>
                </property>
            </activation>
            <properties>
                <vaadin.productionMode>true</vaadin.productionMode>
            </properties>

            <dependencies>
                <dependency>
                    <groupId>com.vaadin</groupId>
                    <artifactId>flow-server-production-mode</artifactId>
                </dependency>
            </dependencies>

            <build>
                <plugins>
                    <plugin>
                        <groupId>com.vaadin</groupId>
                        <artifactId>vaadin-maven-plugin</artifactId>
                        <version>${vaadin.version}</version>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>copy-production-files</goal>
                                    <goal>package-for-production</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>

Pekka3 · November 11, 2018, 12:26pm

To me those steps are working fine - after I’ve edited the pom.xml, IntelliJ asks me to “reimport the maven project”, I click that (can also be done from the project view with right click → maven → reimport). Then I just trigger jetty:run from maven projects view → my-starter-project → plugings → jetty → jetty:run and it “just works”.

Basil3 · November 11, 2018, 9:13pm

Pekka Hyvönen:
To me those steps are working fine - after I’ve edited the pom.xml, IntelliJ asks me to “reimport the maven project”, I click that (can also be done from the project view with right click → maven → reimport). Then I just trigger jetty:run from maven projects view → my-starter-project → plugings → jetty → jetty:run and it “just works”.

Indeed, the POM re-imports, the project builds, and the app runs in Jetty (or with Tomcat externally).

But look at <version>${vaadin.version}</version> in the profile at bottom of the POM. There I have ${vaadin.version} in red colored text (in the IntelliJ editor). Upon mouse-hover, we see error: Plugin 'com.vaadin:vaadin-maven-plugin:12.0.0.beta1' not found

I suspect this is a non-issue in development, as we are both running the project without using that defined production-mode profile.

See attached screenshot in next posting.

Basil3 · November 11, 2018, 9:14pm

POM error screenshot attached.

Basil3 · November 16, 2018, 5:23am

Suddenly got it all working. Perhaps I fixed a boo-boo on my end, but actually I believe some Maven or Vaadin repositories got updated. Thanks for all the help in posts above.

As of 2018-11-15, for Vaadin 12.0.0.beta2, take a working project such as one created from “Project Base” on the Vaadin pago of starter-packs, and make the following changes.

(1)

Refresh your local cache for Maven.

In IntelliJ 2018, choose Preferences/Settings > Build, Execution, Deployment > Build Tools > Maven > Repositories > Update (button). See attached screenshot.

(2)

Change this:

<vaadin.version>11.0.2</vaadin.version>

… to this:

 <vaadin.version>12.0.0.beta2</vaadin.version>

(3)

Inside the repositories element, add this:

    <repository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </repository>

(4)

Below the repositories element, add this:

<pluginRepositories>
    <!-- Repository needed for prerelease versions of Vaadin -->
    <pluginRepository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
    </pluginRepository>
</pluginRepositories>

(5)

Perform a Maven clean and install.

Verify that your POM reports no errors.

Here is a complete working POM.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns = "http://maven.apache.org/POM/4.0.0"
         xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation = "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.basilbourque.acme</groupId>
    <artifactId>acme</artifactId>
    <name>Acme</name>
    <version>1.0-SNAPSHOT</version>
    <packaging>war</packaging>

    <properties>
        <maven.compiler.source>10</maven.compiler.source>
        <maven.compiler.target>10</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <failOnMissingWebXml>false</failOnMissingWebXml>

        <!--<vaadin.version>11.0.2</vaadin.version>-->
        <!--Change above line to line below for alphas-betas-->
        <vaadin.version>12.0.0.beta2</vaadin.version>
    </properties>

    <repositories>
        <!-- Repository used by many Vaadin add-ons -->
        <repository>
            <id>Vaadin Directory</id>
            <url>http://maven.vaadin.com/vaadin-addons</url>
        </repository>

        <!--Add this for alphas-betas-->
        <repository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </repository>

    </repositories>

    <!--Add this for alphas-betas-->
    <pluginRepositories>
        <!-- Repository needed for prerelease versions of Vaadin -->
        <pluginRepository>
            <id>vaadin-prereleases</id>
            <url>https://maven.vaadin.com/vaadin-prereleases</url>
        </pluginRepository>
    </pluginRepositories>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>com.vaadin</groupId>
                <artifactId>vaadin-bom</artifactId>
                <type>pom</type>
                <scope>import</scope>
                <version>${vaadin.version}</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-core</artifactId>
        </dependency>

        <!-- Added to provide logging output as Flow uses -->
        <!-- the unbound SLF4J no-operation (NOP) logger implementation -->
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
        </dependency>

        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.1.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <!-- Jetty plugin for easy testing without a server -->
            <plugin>
                <groupId>org.eclipse.jetty</groupId>
                <artifactId>jetty-maven-plugin</artifactId>
                <version>9.4.11.v20180605</version>
                <configuration>
                    <scanIntervalSeconds>1</scanIntervalSeconds>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <profiles>
        <profile>
            <!-- Production mode can be activated with either property or profile -->
            <id>production-mode</id>
            <activation>
                <property>
                    <name>vaadin.productionMode</name>
                </property>
            </activation>
            <properties>
                <vaadin.productionMode>true</vaadin.productionMode>
            </properties>

            <dependencies>
                <dependency>
                    <groupId>com.vaadin</groupId>
                    <artifactId>flow-server-production-mode</artifactId>
                </dependency>
            </dependencies>

            <build>
                <plugins>
                    <plugin>
                        <groupId>com.vaadin</groupId>
                        <artifactId>vaadin-maven-plugin</artifactId>
                        <version>${vaadin.version}</version>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>copy-production-files</goal>
                                    <goal>package-for-production</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>

ollit.1 · November 16, 2018, 8:12am

Thanks for the post! I think the biggest gotcha there is that you need to update both the repositories and the pluginRepositories to use prereleases.

Pekka3 · November 16, 2018, 8:37am

Now it is also possible to get the latest prerelease versions of every starter from https://vaadin.com/start/pre-release

Basil3 · November 29, 2019, 11:51pm

Pekka Hyvönen:
Now it is also possible to get the latest prerelease versions of every starter from https://vaadin.com/start/pre-release

Not any longer.

https://vaadin.com/start/pre-release
…forwards to:
https://vaadin.com/start/latest

Basil3 · November 29, 2019, 11:54pm

FYI, I have this issue asked and answered on Stack Overflow:

[Configure Maven pom to access Vaadin 14 alpha/beta pre-release]
(https://stackoverflow.com/q/57910701/642706)

Basil3 · May 10, 2020, 10:51pm

Pekka Hyvönen:
Now it is also possible to get the latest prerelease versions of every starter from https://vaadin.com/start/pre-release

On that page I see Version 16 (Pre-release), but not [Vaadin 14.2.0.beta1]
(https://github.com/vaadin/platform/releases/tag/14.2.0.beta1).

So apparently, that page only lists future generations (first part of version number), but not previews of updates (second part of version numbers).