Can't download spring-boot-thin-launcher from a local mirror

I’m trying to force download the launcher from a local mirror using thin.repo key (from the sources)

mvn package -Dthin.repo=http://nexus.local/repository/maven-public/

but doesn’t work. Always try to download from repo.spring.io.

I also have a custom settings.xml in .m2 but is ignore or overriding by launcher pom.

In the sources, it looks like it could use thin.repo property but is ignored.

Any suggestion.

[dsyer]

That’s a better docker strategy TBH than using the thin launcher (but as I said above you can improve it by using the application main class).

I have reproduced the original issue. It’s incredibly fiddly to get the networks set up, but it is possible. I’m not sure I could automate it, but I can probably document it at least.

FWIW I could run mvn package on the simple sample, and it would build a thin (executable) jar and then fail on the thin-maven-plugin. Here’s the error:

...
[ERROR] Failed to execute goal org.springframework.boot.experimental:spring-boot-thin-maven-plugin:1.0.14.RELEASE:resolve (resolve) on project simple: Execution resolve of goal org.springframework.boot.experimental:spring-boot-thin-maven-plugin:1.0.14.RELEASE:resolve failed.: NoSuchElementException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.springframework.boot.experimental:spring-boot-thin-maven-plugin:1.0.14.RELEASE:resolve (r...
...
Caused by: java.util.NoSuchElementException
	at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:721)
	at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:742)
	at org.springframework.boot.experimental.maven.ThinJarMojo.resolveFile(ThinJarMojo.java:84)
	at org.springframework.boot.experimental.maven.ResolveMojo.execute(ResolveMojo.java:102)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	... 28 more

The executable jar is also not executable until the launcher is cached locally. To do that (which would be another workaround for you), you can specify --thin.repo=http://<your-mirror> on the command line when you run it. I think to close this issue we need a way to do that in the Maven plugin as well.

N.B. even if the launcher is cached locally, the Maven plugin still fails. So that’s what I plan to fix first.

[dsyer]

That’s not really a workaround: that’s the best way to build a single fixed docker container for a Spring Boot app. It would start quicker if you used the main class instead of the JarLauncher, but that’s irrelevant for the file system layers.