-
Notifications
You must be signed in to change notification settings - Fork 65
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
[MDEPLOY-314] Include artifactId in DeployMojo#processProject messages #45
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I believe it is worth to look at m-install-p as it has pretty much same/similar places to update... |
merged w/ tweaks as b9c1c8b |
} | ||
} else { | ||
throw new MojoExecutionException( | ||
"The packaging for this project did not assign a file to the build artifact"); | ||
throw new MojoExecutionException("The packaging plugin for project " + project.getArtifactId() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"packaging plugin"?
there is no packaging plugin, just packaging
@@ -299,18 +300,19 @@ private void processProject(final MavenProject project, DeployRequest request) t | |||
} else if (!project.getAttachedArtifacts().isEmpty()) { | |||
if (allowIncompleteProjects) { | |||
getLog().warn(""); | |||
getLog().warn("The packaging plugin for this project did not assign"); | |||
getLog().warn("The packaging plugin for project " + project.getArtifactId() + " did not assign"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same "packaging plugin" issue
The PR addresses MDEPLOY-314 by including the artifact ID of the currently processed project in
MojoExecutionException
and warning messages.[MDEPLOY-XXX] - Fixes bug in ApproximateQuantiles
, where you replaceMDEPLOY-XXX
with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message.mvn clean verify
to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.mvn -Prun-its clean verify
).To make clear that you license your contribution under the Apache License Version 2.0, January 2004 you have to acknowledge this by using the following check-box.