You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ 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]
The text was updated successfully, but these errors were encountered:
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.
I get this warning during maven packaging:
The text was updated successfully, but these errors were encountered: