For background: I'm using dependency:go-offline to build docker base images which have at least some of /root/.m2 pre-populated before they're used for downstream multistage docker builds.
I found this issue when upgrading from 3.8.8 to 3.9.6, then further narrowed it down to being caused by a change in 3.9.3. The following example pom works fine when executing mvn dependency:go-offline using maven 3.9.2, but 3.9.3 and subsequent versions error with: "Could not find artifact commonj.sdo:commonj.sdo:jar:2.1.1.v201112051852 in central" Which is odd because: (1) 3.9.2 works (2) as far as I can tell commonj.sdo is a dependency of sdo-eclipselink-plugin, which is explicitly excluded in the pom (3) maven 3.9.6 will compile / package / install / deploy the project just fine, it just doesn't want to go-offline Would greatly appreciate any pointers or workarounds from the group - this one's got me confused. pom dependency to reproduce the odd behavior (I used an otherwise-empty pom): <dependency> <groupId>com.sun.xml.ws</groupId> <artifactId>jaxws-ri</artifactId> <version>2.3.1</version> <type>pom</type> <exclusions> <exclusion> <groupId>com.sun.xml.ws</groupId> <artifactId>sdo-eclipselink-plugin</artifactId> </exclusion> <exclusion> <groupId>com.sun.xml.ws</groupId> <artifactId>jaxws-rt</artifactId> </exclusion> <exclusion> <groupId>com.fasterxml.woodstox</groupId> <artifactId>woodstox-core</artifactId> </exclusion> </exclusions> </dependency>