Skip to content

fix: Do not run any Maven goals automatically in Eclipse / VS Code (#13302) (CP: 23.0) - #13308

Merged
caalador merged 1 commit into
23.0from
cherry-pick-13302-to-23.0-1647419043214
Mar 16, 2022
Merged

caalador merged 1 commit into
23.0from
cherry-pick-13302-to-23.0-1647419043214

Conversation

@vaadin-bot

Copy link
Copy Markdown
Collaborator

No description provided.

…13302)

It seems like especially VS Code can start running `prepare-frontend` over and over again in some cases which will interfere with an externally running `mvn spring-boot:run` process that will continuously restart because of an updated `target/classes/META-INF/VAADIN/config/flow-build-info.json`

There should be no need nowadays to run `prepare-frontend` from Eclipse at all as it is run through the dev server if needed.
@sonarqubecloud

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 15 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@github-actions

Copy link
Copy Markdown
Contributor

Unit Test Results

   945 files     945 suites   39m 53s ⏱️
6 156 tests 6 107 ✔️ 49 💤 0 ❌
6 368 runs  6 313 ✔️ 55 💤 0 ❌

Results for commit 8d2d535.

@caalador
caalador merged commit ac8bb75 into 23.0 Mar 16, 2022
@caalador
caalador deleted the cherry-pick-13302-to-23.0-1647419043214 branch March 16, 2022 09:16
@vaadin-bot

Copy link
Copy Markdown
Collaborator Author

This ticket/PR has been released with Vaadin 23.0.3.

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.

3 participants