Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Conversation

apeteri
Copy link
Contributor

@apeteri apeteri commented Nov 20, 2023

The PR addresses MDEPLOY-314 by including the artifact ID of the currently processed project in MojoExecutionException and warning messages.


  • Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MDEPLOY-XXX] - Fixes bug in ApproximateQuantiles, where you replace MDEPLOY-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.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (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.

Copy link
Member

@cstamas cstamas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@cstamas
Copy link
Member

cstamas commented Nov 20, 2023

I believe it is worth to look at m-install-p as it has pretty much same/similar places to update...

@cstamas
Copy link
Member

cstamas commented Apr 24, 2024

merged w/ tweaks as b9c1c8b

@cstamas cstamas closed this Apr 24, 2024
}
} 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()
Copy link
Member

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");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same "packaging plugin" issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants