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

Warning during maven package #59

Open
alanorth opened this issue Nov 21, 2022 · 1 comment
Open

Warning during maven package #59

alanorth opened this issue Nov 21, 2022 · 1 comment

Comments

@alanorth
Copy link

I get this warning during maven packaging:

$ mvn package
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for fr.cirad:gigwa2:war:2.5.1-RELEASE
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.codehaus.mojo:exec-maven-plugin @ line 344, column 12
[WARNING] 'profiles.profile[bundles].plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.codehaus.mojo:exec-maven-plugin @ line 979, column 14
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
@GuilhemSempere
Copy link
Collaborator

I'm not the person who originally wrote the Maven build XML, but I remember him telling me it's really a mess to get it to work (I had a chance to confirm that on occasions when I had no choice but to amend it). And since I'm not a Maven pro, my policy here is to live with the warning.

I think the problem is we have a default build section that requires executing some commands, and a second, profile-scoped, build, that also requires executing some commands. I really don't know why Maven wouldn't let users launch commands several times during the build (unless it's actually possible if configured differently?). Maybe a different plugin could be used to workaround that issue?

I'm afraid I'm not going to be able to dig into this in a near future. If a Maven wizard wants to submit a solution, I'll be happy to merge it.

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

No branches or pull requests

2 participants