Vaadin 25 CI build fails: Commercial features require a subscription

General
1

Hello,

I’m having an issue with a Vaadin 25 project running in our Azure DevOps CI pipeline.
The frontend build fails with the error:

Commercial features require a subscription.
Your application contains the following commercial components and no license was found:

  • vaadin-chart
  • vaadin-rich-text-editor

Notes and context:

  • Maven version: 3.9.12

  • Java version: 21.0.9 (Temurin)

  • Vaadin Maven Plugin: com.vaadin:vaadin-maven-plugin:25.0.0

  • Build command in Azure DevOps:

  • (In the actual pipeline *** is replaced by a secret variable that contains the full server license key.)

  • We are using the Server license key – New versions (v23.2 and above / v14.9 and above) from the Vaadin account page, copied as‑is into a secret variable in Azure DevOps (variable group).

  • In pom.xml we have:

  • The same project used to build correctly before upgrading to Vaadin 25.

  • Locally, on a developer machine, the project runs fine with the license (no error shown).

  • The problem appears only in the Azure DevOps build agent.

I’m attaching a screenshot of the Azure DevOps build log where you can see the full error message.

Could you please help me understand:

  1. Whether the configuration above is correct for Vaadin 25 in CI, using a server license key.
  2. If there are any changes in how commercial licenses are validated starting from Vaadin 25 (e.g. new property names, different key format, limitations for CI agents, etc.).
  3. If there is any way to get more detailed logging from the license check beyond what the standard Maven output shows.

If you need more details (entire pom.xml, the exact plugin configuration, or a minimal reproducible project), I can provide them privately.

Thank you in advance for your help.

Best regards,

xml<plugin><groupId>com.vaadin</groupId><artifactId>vaadin-maven-plugin</artifactId><version>25.0.0</version><configuration><proKey>${vaadin.proKey}</proKey></configuration></plugin>

textmvn -f pom.xml -q -B -ntp ^  -Dmaven.repo.local=C:\a\_work\21\.m2\repository ^  -Dvaadin.proKey=*** ^  -Dlogback.configurationFile=logback-pipeline.xml ^  -Djava.library.path=target\natives ^  compile vaadin:build-frontend

We have Vaadin PRO License (Company: AON Italy (Globalsafe)

2

Just a note: there is no such proKey setting for the Maven plugin configuration; it can only be provided as an environment variable, system property (as you do in the command line), or file in the .vaadin folder.

3

Could you please attach the build log after running Maven with -X ?
Logs from the build-fronted execution should be enough.
Please make sure to remove any sensible information

4

You might wanna use the latest version and not the very first version of a new major.

2 Likes