Stop spurious warnings when using a pathing jar

I’m new to Spring, on a team developing on Windows.

To work around issues on Windows and the command line limit of 32767 characters, the concept of a “pathing jar” was created. I first came across it at http://tuhrig.de/gradles-bootrun-and-windows-command-length-limit/. This also seems to be an integrated option in at least one IDE (IntelliJ).

However, when a pathing jar is used with Spring, it results in many spurious warnings about entries not existing, e.g. https://github.com/spring-projects/spring-boot/issues/10111

The relevant code is here in the master branch:

https://github.com/spring-projects/spring-boot/blob/35c6b83fce86a83e4b2b9ec9fb5cbe0646eb23a5/spring-boot-project/spring-boot-devtools/src/main/java/org/springframework/boot/devtools/restart/ChangeableUrls.java#L162-L185

The warnings happen because the code always tries to fixup each classpath entry, believing they always represent relative URLs. I would suggest that this check be changed slightly, to use File.isAbsolute() to see if the entry is already an absolute path, when building the referenced URL.

Is that a change that makes sense to make, and would it be accepted?

[thauk-copperleaf]

Thanks for the help. Closing ticket and hoping that others who run into this problem find it with their favourite search engine 😃

[thauk-copperleaf]

@wilkinsona Thanks for the replies this morning. 😃

I originally tried not stripping the file:// scheme, with 1.5.6, and it didn’t help. I have a log from that run, but perhaps I ran it incorrectly. The log above is from a run with 1.5.8 and stripping the scheme.

Updating our build to 1.5.8 and not stripping the scheme seems to work fine on Windows 7. I’ve just asked that coworkers test on the other 3 platforms we use to ensure our build is working.