Maven problem in 15.0.4
See original GitHub issueUpdate project pom.xml:
<!-- Dependencies -->
<vaadin.version>15.0.4</vaadin.version>
Then error:
<plugin>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-maven-plugin</artifactId>
<version>${vaadin.version}</version>
<executions>
------> <execution>
<goals>
<goal>prepare-frontend</goal>
</goals>
</execution>
</executions>
</plugin>
Error: Plugin execution not covered by lifecycle configuration: com.vaadin:vaadin-maven-plugin:15.0.4:prepare-frontend (execution: default, phase: process-resources)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Cannot build any maven project with same error
It has been few weeks since I build anything in maven, and I just tried to build one of the projects and it...
Read more >Fixing Vulnerabilities in Maven-Based Projects - Foojay
In this article, I will explain how you can fix vulnerabilities in third-party libraries when using Maven, even when it is not obvious....
Read more >How to Fix Invalid Target Release: 1.7, 1.8, 1.9, or 1.10 Error ...
The root cause of the problem is that you have specified a higher Java version in your pom.xml file for the Maven compiler...
Read more >Maven Tycho for building Eclipse plug-ins, OSGi bundles and ...
Re-run your build and ensure that is still runs successfully. 5.2. Potential error resolution with the usage Java version. If you are using...
Read more >Release Notes – Maven 3.6.1
An issue has been fixed causing multiple executions of plugin goals, related to using parallel build options like mvn plugin:goal -T 4 ....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Exact same problem as @DManstrator
Probably caused by https://github.com/vaadin/flow/commit/e740b880e01fd773e13cc41b90934ecc4de52f51#diff-edb73af5d80cb83b99c25aea7abf12b0 which incorrectly states that
prepare-frontend
should be both ignored and executed