Glad that it was resolved.
Still, I have to add a remark: purging your local repo (literally "nuking",
just rm -r ~/.m2/repository) is "good thing" and should be part of regular
"workstation hygiene" just like updating OS and tools is.
Remember, that "local repo" is, as you rightfully say "a
Ah ha! It *was* the Maven cache. Thank you for getting me to take another
look.
I had been looking at the files for the transient library, xml-apis. That
all checked out. Just now I looked one higher, at the library that was
bringing in xml-apis (com.megginson.sax:xml-writer:0.2). *That* didn't
Any chance there are some conflicting profile or differences in settings.xml on
the different machines?
Maybe maven caches is different and needs cleanup?
Eric Bresie
ebre...@gmail.com (mailto:ebre...@gmail.com)
> On April 16, 2023 at 7:36:36 AM CDT, Thad Humphries
There are no profiles in the pom.xml that brings in the jar in question,
xml-apis (
https://repo1.maven.org/maven2/com/megginson/sax/xml-writer/0.2/xml-writer-0.2.pom).
Since the webapp works without it, I'll exclude it from the build.
On Sat, Apr 15, 2023 at 7:30 PM Tomo Suzuki
wrote:
> > The
Thanks for the link about Xerces. We've had run-ins with it in the past.
For now I'm going with your recommendation to exclude xml-apis from the
build. The com.megginson.sax:xml-writer is used in one place, and that is
working fine (though I'll make a note in the pom about it).
On Sat, Apr 15,
> The pom.xml has 2 profiles
I meant the pom file that delcares the missing dependency. Your
(transitive) dependency's pom.xml.
On Sat, Apr 15, 2023 at 13:29 Thad Humphries
wrote:
> Thanks. I might be missing something but I can't see it. Responses inline.
>
> On Sat, Apr 15, 2023 at 12:00 PM
Ok, thanks.
A reproducer would be great.
But FTR, this is what I get (mvn 3.9.1, bf, "normal" and "verbose"):
https://gist.github.com/cstamas/7f027113d872e1b9941337916931c724
T
On Sat, Apr 15, 2023 at 11:04 PM Greg Chabala
wrote:
> >
> > Are you saying that Maven dependency resolving is not
>
> Are you saying that Maven dependency resolving is not deterministic?
>
I expect the resolution to be deterministic. But from all that has been
shared here so far, it looks like something non-deterministic is happening,
or perhaps more accurately, it is deterministic per machine, but varies
Greg,
Are you saying that Maven dependency resolving is not deterministic?
Thanks
T
On Sat, Apr 15, 2023 at 7:50 PM Greg Chabala wrote:
> It's no surprise that Xerces is involved here. Some colorful background:
>
>
If the versions of Maven (hence of the dependency resolution lib) and
maven-dependency-plugin (might interpret trees differently, but given
maven-war-plugin also behaves differently I'd rather blame Maven) are the
same, and you have no differing extension neither, then I have no idea
sorry.
Le
It's no surprise that Xerces is involved here. Some colorful background:
https://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven
The crux is clearly that xml-apis is a transitive dependency in two places,
and depending on which is elected vs evicted, it will be compile
Thanks. I might be missing something but I can't see it. Responses inline.
On Sat, Apr 15, 2023 at 12:00 PM Tomo Suzuki
wrote:
> My guess
>
> - Maven profiles activated based on environment
>
The pom.xml has 2 profiles, both triggered by -P, not (that I know of) by
the environment. In any
My guess
- Maven profiles activated based on environment
- Download URL was unavailable
or
- Disk was full when downloading
On Fri, Apr 14, 2023 at 15:34 Thad Humphries
wrote:
> 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
Answers inline:
On Fri, Apr 14, 2023 at 4:16 PM Greg Chabala wrote:
> > I have *war that I've built on 3 different Macs (maven-war-plugin 3.3.2).
> >
>
> Is there a reason you're rebuilding your WAR three times on different Macs?
>
One Mac Mini is my home machine, the other is the office
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] | +-
> I have *war that I've built on 3 different Macs (maven-war-plugin 3.3.2).
>
Is there a reason you're rebuilding your WAR three times on different Macs?
> The code is pulled from my local git repo, and the supporting jars are from
> a local Nexus repository.
Are they all building from the
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 a
écrit :
> I have *war that I've built on 3 different
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
18 matches
Mail list logo
