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
The documentation for the classpath index section of nested jars should mention the different behaviour if reproducible builds are enabled. [1]
I ran into issues with classpath order after enabling reproducible maven builds (different, outdated JAXB implementation picked up) and came across that page. Since there was no mention of reproducible builds, I suspected a bug and looked at the source code responsible for classpath.idx.
Sorry, I'm not sure what you're suggesting. We already document the fact that the order in the index file matches the order that's used by the build system. What more did you want to see? I'm a little reluctant to mention specifics as there are lots of ways in which a build system's classpath ordering can be changed and we don't want to try to document them all.
Thanks. I'd forgotten that Maven doesn't apply reproducible ordering consistently and that there's some logic in its war plugin that we had to replicate. I agree that this is worth documenting if it only applies when packaging and not to when running (spring-boot:run) or testing the application.
The documentation for the classpath index section of nested jars should mention the different behaviour if reproducible builds are enabled. [1]
I ran into issues with classpath order after enabling reproducible maven builds (different, outdated JAXB implementation picked up) and came across that page. Since there was no mention of reproducible builds, I suspected a bug and looked at the source code responsible for classpath.idx.
[1]
spring-boot/spring-boot-project/spring-boot-docs/src/docs/antora/modules/specification/pages/executable-jar/nested-jars.adoc
Line 99 in 70a5dc6
The text was updated successfully, but these errors were encountered: