Except for the times, the effective poms are identical between the two Mac Minis.
>From the dependency trees, I see what I see in the debug output. The build without the xml-apis-1.0.b2.jar shows (condensing) [INFO] +- com.google.gwt:gwt-dev:jar:2.8.2:provided [INFO] | +- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided [INFO] | | +- xerces:xercesImpl:jar:2.11.0:provided [INFO] | | | \- xml-apis:xml-apis:jar:1.4.01:provided [INFO] | | +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided ... [INFO] +- com.megginson.sax:xml-writer:jar:0.2:compile while the other shows [INFO] +- com.google.gwt:gwt-dev:jar:2.8.2:provided [INFO] | +- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided [INFO] | | +- xerces:xercesImpl:jar:2.11.0:provided [INFO] | | +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided ... [INFO] +- com.megginson.sax:xml-writer:jar:0.2:compile [INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile So for some reason the machines see a different requirement for xml-apis-*.jar On Fri, Apr 14, 2023 at 4:12 PM Thomas Broyer <t.bro...@gmail.com> wrote: > Have you tried diffing the effective-pom on the various machines? > How about running with debug logs? Does the waven-war-plugin maybe outputs > why it picks or excludes dependencies from the war? > > Le ven. 14 avr. 2023 à 21:34, Thad Humphries <thad.humphr...@gmail.com> a > écrit : > > > I have *war that I've built on 3 different Macs (maven-war-plugin 3.3.2). > > The code is pulled from my local git repo, and the supporting jars are > from > > a local Nexus repository. All Macs use the same setup--Amazon Corretto > Java > > 11 and Maven 3.9.1. The ~/.m2/settings.xml are identical. Two of the Macs > > produce the same *war (a Mini with 10.15.7 and a MacBook with 12.6.5). > The > > third Mac--also a Mini with 10.15.7--is missing one JAR file in > > WEB-INF/lib. How can this be? > > > > The missing JAR is in each local repository. I do not see this JAR when I > > run `mvn dependency:tree`, though I see a different (newer) version as > > "provided." The missing JAR doesn't seem to matter when the webapp runs > (no > > problems found so far). Any idea as to why, and what I can (or should?) > do > > for a consistent build? > > > > -- > > "Hell hath no limits, nor is circumscrib'd In one self-place; but where > we > > are is hell, And where hell is, there must we ever be" --Christopher > > Marlowe, *Doctor Faustus* (v. 111-13) > > > -- "Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, *Doctor Faustus* (v. 111-13)
