Vaadin 7.7.42 build search Vaadin Charts 4 after revert from 7.7.48 (JDK 17)

Vaadin 6 / 7 / 8
1

a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

Hi Vaadin Team,

I’m encountering a build issue after upgrading a project from Vaadin 7.7.42 to 7.7.48 and then reverting back to 7.7.42. Following the revert, the Maven build now attempts to resolve Vaadin Charts 4, even though the project explicitly depends on vaadin-charts 3.3.1 and we do not use Charts 4 anywhere in the codebase.

Environment

  • JDK: 17
  • Vaadin Framework: 7.7.42 (reverted from 7.7.48)
  • Vaadin Charts: 3.3.1

Generic error observed during build (widgetset compilation):

Failed to execute goal com.vaadin:vaadin-maven-plugin:7.7.42:compile (default) on project webapp:
Command [...] failed with status 1

What I’ve tried

  • Fresh repository clone
  • Deleted ~/.m2/repository completely
  • Reinstalled IntelliJ IDEA (clean install, different version)
  • Multiple mvn clean install runs
  • Verified no dependency or POM changes that would introduce Charts 4
  • Confirmed the widgetset definition still references the original modules only

Issue summary After the upgrade and revert, the widgetset compilation behaves as if there are stale or upgraded GWT/Charts artifacts, and specifically tries to look for Vaadin Charts 4 instead of using Charts 3.3.1.

Questions

  1. Does upgrading from 7.7.42 → 7.7.48 introduce widgetset metadata, module references, or cache artifacts that could cause the compiler to resolve Charts 4 even after reverting?
  2. Is there any known interaction between Vaadin 7.7.48 and vaadin-charts 3.3.1 that could cause transitive or persisted references to Charts 4?
  3. What are the recommended steps to fully reset widgetset outputs and caches (beyond mvn clean and wiping ~/.m2)—including any Vaadin/GWT persistent unit cache locations—especially when using JDK 17?
  4. Could JDK 17 contribute to this behavior with the Vaadin 7.7.x widgetset compiler, and are there version constraints we should observe?

Any guidance to ensure the build uses vaadin-charts 3.3.1 and to prevent resolution of Charts 4 would be greatly appreciated.

Thank you

2

I was told by your colleague that you got the issue resolved and it was configuration issue on your side.