Skip to content

chore: pin maven-install-plugin to 3.1.4 - #25226

Merged
Artur- merged 1 commit into
mainfrom
bump-maven-install-plugin
Aug 17, 2026
Merged

Artur- merged 1 commit into
mainfrom
bump-maven-install-plugin

Conversation

@Artur-

@Artur- Artur- commented Aug 15, 2026 •

Copy link
Copy Markdown
Member

Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
default lifecycle bindings. That version predates the Resolver-based
installer and still writes repository metadata through the legacy
ArtifactInstaller API. The group level com/vaadin/maven-metadata-local.xml
is shared by every maven-plugin packaging module, so flow-maven-plugin and
flow-dev-bundle-plugin both write it during the -T builds CI runs.

Pinning 3.1.4 puts installation on the Resolver API for every module
regardless of which Maven version builds the project.

@vaadin-bot

Copy link
Copy Markdown
Collaborator

@Artur- this "chore:"/"test:" PR has been approved automatically, but auto merge has not been enabled for it. You can enable the auto merge by yourself, or ask another member for another review. [Message is sent from bot]

@github-actions

github-actions Bot commented Aug 15, 2026 •

Copy link
Copy Markdown
Contributor

Test Results

 1 450 files  ±0   1 451 suites  ±0   1h 31m 54s ⏱️ + 2m 31s
10 444 tests ±0  10 377 ✅ ±0  67 💤 ±0  0 ❌ ±0 
10 880 runs  ±0  10 812 ✅ ±0  68 💤 ±0  0 ❌ ±0 

Results for commit f6d673a. ± Comparison against base commit 609b060.

♻️ This comment has been updated with latest results.

Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
default lifecycle bindings. That version predates the Resolver-based
installer and still writes repository metadata through the legacy
ArtifactInstaller API. The group level com/vaadin/maven-metadata-local.xml
is shared by every maven-plugin packaging module, so flow-maven-plugin and
flow-dev-bundle-plugin both write it during the -T builds CI runs.

Pinning 3.1.4 puts installation on the Resolver API for every module
regardless of which Maven version builds the project.
@cla-assistant

cla-assistant Bot commented Aug 15, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@vaadin-bot

Copy link
Copy Markdown
Collaborator

@Artur- this "chore:"/"test:" PR has been approved automatically, but auto merge has not been enabled for it. You can enable the auto merge by yourself, or ask another member for another review. [Message is sent from bot]

@sonarqubecloud

Copy link
Copy Markdown

@Artur-

Artur- commented Aug 16, 2026

Copy link
Copy Markdown
Member Author

@claude is this correct and would only updating the Maven version to 3.9 help?

@claude

claude Bot commented Aug 16, 2026 •

Copy link
Copy Markdown

Claude finished @Artur-'s task in 1m 14s —— View job


Answer

Yes, the diagnosis is correct, and I dug into the repo to confirm the details.

On correctness of the PR reasoning:

  • CI does pin the runtime Maven to 3.8.7 — .github/workflows/validation.yml sets maven-version: 3.8.7 in most jobs (with one outlier job on 3.9.2 at line 462), and claude.yml also uses 3.8.7.
  • Maven 3.8.7's default lifecycle bindings resolve install to maven-install-plugin:2.4, which predates the Resolver-based installer and writes metadata through the legacy ArtifactInstaller API.
  • Both flow-maven-plugin and flow-dev-bundle-plugin are maven-plugin packaging, so they each write the shared group-level com/vaadin/maven-metadata-local.xml (used for plugin-prefix resolution). Under -T parallel builds, the legacy 2.4 installer merges this shared metadata non-atomically → the race you're seeing. Pinning 3.1.4 routes installation through the Resolver, which handles metadata far more safely. So the fix is sound.

⚠️ One thing worth clarifying: the <maven.version>3.9.16</maven.version> property already in pom.xml is not the build runtime — it's the maven-core/maven-plugin-api dependency version the plugin modules compile against (see flow-plugins/*/pom.xml). It doesn't influence which install plugin the lifecycle binds.

Would only updating the runtime Maven to 3.9 help?

  • Yes, as an alternative — Maven 3.9.x's default lifecycle bindings pull maven-install-plugin:3.1.x (Resolver-based), so bumping setup-maven to 3.9 would make the immediate CI corruption go away too.
  • But pinning in pom.xml is the better/more complete fix, and the two aren't mutually exclusive:
    • It's independent of the runtime — it protects local developer builds and any job still on 3.8.x (today there's a mix: several 3.8.7 jobs + one 3.9.2 job). Bumping only CI leaves anyone on 3.8 exposed.
    • It's explicit and self-documenting (the comment in the diff makes the intent clear), rather than relying on an implicit default-binding behavior that changes between Maven versions.
    • It's low risk — it only affects the install goal.

Recommendation: keep this PR as-is (it's the robust fix). Optionally, as a separate follow-up, you could also bump the setup-maven runtime to 3.9 to pick up other Resolver improvements — but that's orthogonal and larger, and shouldn't block this change.


  • Read the diff and repo context
  • Verify CI's pinned Maven version and default plugin bindings
  • Answer the question
    · bump-maven-install-plugin

@Artur-
Artur- added this pull request to the merge queue Aug 17, 2026
Merged via the queue into main with commit 9b1be6a Aug 17, 2026
35 checks passed
@Artur-
Artur- deleted the bump-maven-install-plugin branch August 17, 2026 06:41
totally-not-ai Bot added a commit that referenced this pull request Aug 28, 2026
The pin is backported to 25.2 separately, so keep this PR to the revert
of the CI metadata cleanup workaround only.
@vaadin-bot

Copy link
Copy Markdown
Collaborator

Hi @Artur- and @Artur-, when i performed cherry-pick to this commit to 25.1, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 9b1be6a
error: could not apply 9b1be6a... chore: pin maven-install-plugin to 3.1.4 (#25226)
hint: After resolving the conflicts, mark them with
hint: "git add/rm ", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

Artur- added a commit that referenced this pull request Aug 28, 2026
This branch's copy of validation.yml had drifted a long way from main's.
Since a pull_request workflow runs the copy of the file that lives on the
PR's base branch, none of the fixes made on main since then have applied
to pull requests against this branch.

Ported over:

- The auto-merge job, which approves cherry-picks and low-risk
  chore:/test:/refactor: pull requests. It has been on 24.9 and newer
  since it was introduced but never reached this branch, so pull requests
  here were never auto reviewed. It depends on test-results rather than on
  api-diff-labeling as it does on newer branches, because api-diff-labeling
  is gated on a pull_request_target event this workflow does not subscribe
  to and therefore never runs; the "+0.0.1" label that autoMerge.js looks
  for comes from the TeamCity API-DIFF labeling build instead.
- Main's fork handling. Pull requests from forks now build but run no
  tests and see no secrets, replacing the pr-tests environment and the
  actions-cool/check-user-permission check, which tracked a floating
  @main ref.
- Every action pinned to the commit main pins it to. pnpm/action-setup
  stays on v3, the version 25.2 pins, rather than main's v6, which pairs
  with pnpm 11 rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
  body of a shell script.
- always() for test-results. With failure() || success() the job is
  skipped when a matrix entry is cancelled, and a skipped required check
  satisfies branch protection, which would let auto-merge proceed past a
  cancelled IT.
- The IT reliability fixes: a 22 minute step timeout, detaching mvn's
  stdio so an orphaned child JVM cannot pin the step open, killing
  leftover Java processes, and packaging test reports on cancellation.
- A concurrency group that no longer expands to the literal string
  "<head_ref> || <ref_name>", and merge_group support.
- Dropping the edited pull request trigger, which re-ran the whole suite
  when someone edited a PR title.

It also picks up two changes from main that the cherry-pick bot could not
apply here, because this branch's pom.xml uses different indentation and
pins maven-jar-plugin literally rather than through a property:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
  install:2.4 by default, which corrupts the group level
  com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
  install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
  step downloads Maven on every job and times out intermittently, and the
  ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis, the coverage profile, the
Javadoc-to-JUnit conversion and the spotless formatter workflow. All of
them need build-side support that only exists on 25.2 and newer.
vaadin-bot added a commit that referenced this pull request Aug 28, 2026
This PR cherry-picks changes from the original PR #25226 to branch 25.2.
---
#### Original PR description
> Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
> default lifecycle bindings. That version predates the Resolver-based
> installer and still writes repository metadata through the legacy
> ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
> is shared by every maven-plugin packaging module, so flow-maven-plugin
and
> flow-dev-bundle-plugin both write it during the -T builds CI runs.
> 
> Pinning 3.1.4 puts installation on the Resolver API for every module
> regardless of which Maven version builds the project.
>

Co-authored-by: Artur Signell <artur@vaadin.com>
Artur- added a commit that referenced this pull request Aug 28, 2026
Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
default lifecycle bindings. That version predates the Resolver-based
installer and still writes repository metadata through the legacy
ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
is shared by every maven-plugin packaging module, so flow-maven-plugin
and
flow-dev-bundle-plugin both write it during the -T builds CI runs.

Pinning 3.1.4 puts installation on the Resolver API for every module
regardless of which Maven version builds the project.
Artur- added a commit that referenced this pull request Aug 28, 2026
Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
default lifecycle bindings. That version predates the Resolver-based
installer and still writes repository metadata through the legacy
ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
is shared by every maven-plugin packaging module, so flow-maven-plugin
and
flow-dev-bundle-plugin both write it during the -T builds CI runs.

Pinning 3.1.4 puts installation on the Resolver API for every module
regardless of which Maven version builds the project.
Artur- added a commit that referenced this pull request Aug 28, 2026
Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
default lifecycle bindings. That version predates the Resolver-based
installer and still writes repository metadata through the legacy
ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
is shared by every maven-plugin packaging module, so flow-maven-plugin
and
flow-dev-bundle-plugin both write it during the -T builds CI runs.

Pinning 3.1.4 puts installation on the Resolver API for every module
regardless of which Maven version builds the project.
Artur- added a commit that referenced this pull request Aug 28, 2026
This PR cherry-picks changes from the original PR #25226 to branch 23.7.
---
#### Original PR description
> Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
> default lifecycle bindings. That version predates the Resolver-based
> installer and still writes repository metadata through the legacy
> ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
> is shared by every maven-plugin packaging module, so flow-maven-plugin
and
> flow-dev-bundle-plugin both write it during the -T builds CI runs.
>
> Pinning 3.1.4 puts installation on the Resolver API for every module
> regardless of which Maven version builds the project.

Co-authored-by: Artur Signell <artur@vaadin.com>
Artur- added a commit that referenced this pull request Aug 28, 2026
This PR cherry-picks changes from the original PR #25226 to branch 24.9.
---
#### Original PR description
> Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
> default lifecycle bindings. That version predates the Resolver-based
> installer and still writes repository metadata through the legacy
> ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
> is shared by every maven-plugin packaging module, so flow-maven-plugin
and
> flow-dev-bundle-plugin both write it during the -T builds CI runs.
>
> Pinning 3.1.4 puts installation on the Resolver API for every module
> regardless of which Maven version builds the project.

Co-authored-by: Artur Signell <artur@vaadin.com>
Artur- added a commit that referenced this pull request Aug 28, 2026
This PR cherry-picks changes from the original PR #25226 to branch
24.10.
---
#### Original PR description
> Maven 3.8.7, which CI pins, binds maven-install-plugin 2.4 through its
> default lifecycle bindings. That version predates the Resolver-based
> installer and still writes repository metadata through the legacy
> ArtifactInstaller API. The group level
com/vaadin/maven-metadata-local.xml
> is shared by every maven-plugin packaging module, so flow-maven-plugin
and
> flow-dev-bundle-plugin both write it during the -T builds CI runs.
>
> Pinning 3.1.4 puts installation on the Resolver API for every module
> regardless of which Maven version builds the project.

Co-authored-by: Artur Signell <artur@vaadin.com>
manolo pushed a commit that referenced this pull request Sep 2, 2026
This branch's copy of validation.yml had drifted from main's. Since a
pull_request workflow runs the copy of the file that lives on the PR's
base branch, none of the fixes made on main since then have applied to
pull requests against this branch.

Ported over:

- Main's fork handling. Pull requests from forks now build but run no
tests and see no secrets, replacing the pr-tests environment and the
actions-cool/check-user-permission check, which tracked a floating @main
ref. api-diff-labeling, which has write access to labels, is skipped for
forks for the same reason.
- Every action pinned to the commit main pins it to. pnpm/action-setup
stays on v3, the version 25.2 pins, rather than main's v6, which pairs
with pnpm 11 rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
body of a shell script.
- The head sha is now checked out in build and it-tests as it already
was in unit-tests. Those two jobs checked out the pull request merge ref
instead, so the workspace build saved did not match the sources the unit
tests restoring it ran against.
- The IT reliability fixes: a 22 minute step timeout, detaching mvn's
stdio so an orphaned child JVM cannot pin the step open, killing
leftover Java processes, and packaging test reports on cancellation.
- Dropping the base_ref != 'main' guard on auto-merge, which main
removed when auto-merge was enabled there.
- A concurrency group keyed on the merge group head sha, and merge_group
support.

It also picks up two changes from main that the cherry-pick bot could
not apply here, because this branch's pom.xml uses different indentation
and pins maven-jar-plugin literally rather than through a property:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
install:2.4 by default, which corrupts the group level
com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
step downloads Maven on every job and times out intermittently, and the
ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis, the coverage profile, the
Javadoc-to-JUnit conversion and the spotless formatter workflow. All of
them need build-side support that only exists on 25.2 and newer.
manolo pushed a commit that referenced this pull request Sep 2, 2026
This branch's copy of validation.yml had drifted from main's. Since a
pull_request workflow runs the copy of the file that lives on the PR's
base branch, none of the fixes made on main since then have applied to
pull requests against this branch.

Ported over:

- Main's fork handling. Pull requests from forks now build but run no
tests and see no secrets, replacing the pr-tests environment and the
actions-cool/check-user-permission check, which tracked a floating @main
ref. api-diff-labeling, which has write access to labels, is skipped for
forks for the same reason.
- Every action pinned to the commit main pins it to. pnpm/action-setup
stays on v3, the version 25.2 pins, rather than main's v6, which pairs
with pnpm 11 rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
body of a shell script.
- The head sha is now checked out in build and it-tests as it already
was in unit-tests. Those two jobs checked out the pull request merge ref
instead, so the workspace build saved did not match the sources the unit
tests restoring it ran against.
- The IT reliability fixes: a 22 minute step timeout, detaching mvn's
stdio so an orphaned child JVM cannot pin the step open, killing
leftover Java processes, and packaging test reports on cancellation.
- Dropping the base_ref != 'main' guard on auto-merge, which main
removed when auto-merge was enabled there.
- A concurrency group keyed on the merge group head sha, and merge_group
support.

It also picks up two changes from main that the cherry-pick bot could
not apply here, because this branch's pom.xml uses different indentation
and pins maven-jar-plugin literally rather than through a property:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
install:2.4 by default, which corrupts the group level
com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
step downloads Maven on every job and times out intermittently, and the
ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis, the coverage profile, the
Javadoc-to-JUnit conversion and the spotless formatter workflow. All of
them need build-side support that only exists on 25.2 and newer.
manolo pushed a commit that referenced this pull request Sep 2, 2026
This branch's copy of validation.yml had drifted a long way from main's.
Since a pull_request workflow runs the copy of the file that lives on
the PR's base branch, none of the fixes made on main since then have
applied to pull requests against this branch.

Ported over:

- The auto-merge job, which approves cherry-picks and low-risk
chore:/test:/refactor: pull requests. It has been on 24.9 and newer
since it was introduced but never reached this branch, so pull requests
here were never auto reviewed. It depends on test-results rather than on
api-diff-labeling as it does on newer branches, because
api-diff-labeling is gated on a pull_request_target event this workflow
does not subscribe to and therefore never runs; the "+0.0.1" label that
autoMerge.js looks for comes from the TeamCity API-DIFF labeling build
instead.
- Main's fork handling. Pull requests from forks now build but run no
tests and see no secrets, replacing the pr-tests environment and the
actions-cool/check-user-permission check, which tracked a floating @main
ref.
- Every action pinned to the commit main pins it to. pnpm/action-setup
stays on v3, the version 25.2 pins, rather than main's v6, which pairs
with pnpm 11 rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
body of a shell script.
- always() for test-results. With failure() || success() the job is
skipped when a matrix entry is cancelled, and a skipped required check
satisfies branch protection, which would let auto-merge proceed past a
cancelled IT.
- The IT reliability fixes: a 22 minute step timeout, detaching mvn's
stdio so an orphaned child JVM cannot pin the step open, killing
leftover Java processes, and packaging test reports on cancellation.
- A concurrency group that no longer expands to the literal string
"<head_ref> || <ref_name>", and merge_group support.
- Dropping the edited pull request trigger, which re-ran the whole suite
when someone edited a PR title.

It also picks up two changes from main that the cherry-pick bot could
not apply here, because this branch's pom.xml uses different indentation
and pins maven-jar-plugin literally rather than through a property:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
install:2.4 by default, which corrupts the group level
com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
step downloads Maven on every job and times out intermittently, and the
ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis, the coverage profile, the
Javadoc-to-JUnit conversion and the spotless formatter workflow. All of
them need build-side support that only exists on 25.2 and newer.
manolo pushed a commit that referenced this pull request Sep 2, 2026
This branch's copy of validation.yml had drifted a long way from main's.
Since a pull_request workflow runs the copy of the file that lives on
the PR's base branch, none of the fixes made on main since then have
applied to pull requests against this branch.

Ported over:

- The auto-merge job, which approves cherry-picks and low-risk
chore:/test:/refactor: pull requests. It has been on 24.9 and newer
since it was introduced but never reached this branch, so pull requests
here were never auto reviewed. It depends on test-results rather than on
api-diff-labeling as it does on newer branches, because
api-diff-labeling is gated on a pull_request_target event this workflow
does not subscribe to and therefore never runs; the "+0.0.1" label that
autoMerge.js looks for comes from the TeamCity API-DIFF labeling build
instead.
- Main's fork handling. Pull requests from forks now build but run no
tests and see no secrets, replacing the pr-tests environment and the
actions-cool/check-user-permission check, which tracked a floating @main
ref.
- Every action pinned to the commit main pins it to. pnpm/action-setup
stays on v3, the version 25.2 pins, rather than main's v6, which pairs
with pnpm 11 rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
body of a shell script.
- always() for test-results. With failure() || success() the job is
skipped when a matrix entry is cancelled, and a skipped required check
satisfies branch protection, which would let auto-merge proceed past a
cancelled IT.
- The IT reliability fixes: a 22 minute step timeout, detaching mvn's
stdio so an orphaned child JVM cannot pin the step open, killing
leftover Java processes, and packaging test reports on cancellation.
- A concurrency group that no longer expands to the literal string
"<head_ref> || <ref_name>", and merge_group support.
- Dropping the edited pull request trigger, which re-ran the whole suite
when someone edited a PR title.

It also picks up two changes from main that the cherry-pick bot could
not apply here, because this branch's pom.xml uses different indentation
and pins maven-jar-plugin literally rather than through a property:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
install:2.4 by default, which corrupts the group level
com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
step downloads Maven on every job and times out intermittently, and the
ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis, the coverage profile, the
Javadoc-to-JUnit conversion and the spotless formatter workflow. All of
them need build-side support that only exists on 25.2 and newer.
manolo added a commit that referenced this pull request Sep 2, 2026
…in (#25361)

Since a pull_request workflow runs the copy of the file that lives on
the PR's base branch, fixes made on main only reach pull requests
against this branch once they are ported here.

Ported over:

- Main's fork handling. Pull requests from forks now build but run no
tests and see no secrets, replacing the pr-tests environment.
api-diff-labeling, which has write access to labels, is skipped for
forks for the same reason.
- Every action pinned to the commit main pins it to, including the two
in sonar-pr.yml, which has no equivalent on main to copy from but was
still tracking floating v4 tags. pnpm/action-setup stays on v3, the
version 25.2 pins, rather than main's v6, which pairs with pnpm 11
rather than the pnpm 8 this branch builds against.
- TB_LICENSE passed through env instead of being interpolated into the
body of a shell script.
- Dropping the base_ref != 'main' guard on auto-merge, which main
removed when auto-merge was enabled there.
- A concurrency group keyed on the merge group head sha, so re-running
an obsolete merge queue validation cannot cancel the run validating the
current merge group.
- Dropping the base branch filter from the pull_request trigger in both
workflows, so that pull requests stacked on another feature branch are
validated and format checked too. PRs against an older maintenance
branch keep using that branch's own copy of these files.

It also picks up two changes from main that the cherry-pick bot could
not apply here:

- Pinning maven-install-plugin to 3.1.4 (#25226). Maven 3.8 binds
install:2.4 by default, which corrupts the group level
com/vaadin/maven-metadata-local.xml when maven-plugin packaging modules
install in parallel under -T.
- Using the runner-provided Maven instead of setup-maven (#25265). The
step downloads Maven on every job and times out intermittently, and the
ubuntu-24.04 image already ships Maven 3.9.16.

Deliberately not ported: the Sonar analysis into validation.yml, the
coverage profile it reads, and the Javadoc-to-JUnit conversion. All of
them need build-side support that only exists on 25.2 and newer. Sonar
keeps running from sonar-pr.yml on this branch.

Co-authored-by: Manuel Carrasco Moñino <manolo@vaadin.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants