-
Notifications
You must be signed in to change notification settings - Fork 4
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
Plugin dogfooding #53
Comments
Given resolver distinguishes "existing" (as in, "available from some repository [local or remote]") and "non existing" (as in, "the current POM that may or may not have been built/installed), you need to handle this with care. Toolbox due this introduces two Mojos: maveniverse/toolbox#37 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I previously had the following in
pom.xml
:The idea was to execute the current version of the plugin when running
mvn install
(perhaps it should beverify
, and perhaps this is the solution). This caused problems when building the project on a new machine (but somehow not on CI) where the project didn't exist and so couldn't be executed.I've temporarily removed this execution from the POM, and this ticket is to look at reintroducing it.
The text was updated successfully, but these errors were encountered: