-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npx goal causes "Plugin execution not covered by lifecycle configuration" warning in VS Code #1150
Comments
heathharrelson
added a commit
to heathharrelson/frontend-maven-plugin
that referenced
this issue
Jun 5, 2024
Add npx to lifecycle-mapping-metadata.xml. Fixes eirslett#1150.
heathharrelson
added a commit
to heathharrelson/frontend-maven-plugin
that referenced
this issue
Jun 5, 2024
Add npx to lifecycle-mapping-metadata.xml. Fixes eirslett#1150.
eirslett
pushed a commit
that referenced
this issue
Jun 6, 2024
Add npx to lifecycle-mapping-metadata.xml. Fixes #1150.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
VS Code warns that "Plugin execution not covered by lifecycle configuration" when there is an
npx
execution inpom.xml
.Full error:
There are no errors or warning when I compile on the command line. This is similar to the behavior in #531, and I was able to fix the issue locally by adding
npx
tolifecycle-mapping-metadata.xml
. I can submit a PR if that's desirable.If the current behavior is a bug, please provide the steps to reproduce.
Add an
<execution>
that uses thenpx
goal topom.xml
. In my case, the<build>
section ofpom.xml
looks like this:The cowsay example works just as well.
What is the expected behavior?
An
npx
execution inpom.xml
does not trigger a warning in VS Code.Please mention your frontend-maven-plugin and operating system version.
plugin version: 1.15.0
operating system: macOS Ventura 13.6.3
VS Code: 1.89.1
The text was updated successfully, but these errors were encountered: