When trying to build the Spring Boot source code, I ran into a strange problem: The Gradle build terminated with several "File name too long" exceptions. I knew that the ext4 filesystem I was using has limits - 4064 characters for the entire path and 255 characters for each segment. But I didn't seem to hit that limit. Something strange was going on.

This was the error message I encountered:

Build file '/home/matthias/IdeaProjects/spring-boot/spring-boot-project/spring-boot-starters/spring-boot-starter-parent/build.gradle' * What went wrong: Could not compile build file '/home/matthias/IdeaProjects/spring-boot/spring-boot-project/spring-boot-starters/spring-boot-starter-parent/build.gradle'. > startup failed: /home/matthias/.gradle/caches/7.3.3/scripts/datpeaugopjrqeo19w9544ugq/proj/_BuildScript_$_run_closure1$_closure2$_closure5$_closure8$_closure10$_closure15$_closure24$_closure54$_closure59$_closure61$_closure62$_closure63.class (File name too long)

Very weird, the filename is only 151 characters!

It turns out that because I'm using an encrypted home directory via Gvfs, the actual filenames are longer. This makes sense, you can't expect the encrypted filename to be the same size as the unencrypted one. In fact, all filenames should be the same size so that it's impossible to deduct anything from file lenghts.

The solution was rather simple if unsatisfying: Move the Gradle directory outside the encrypted home directory. Example:

$ mkdir -p /var/tmp/matt/gradle $ export GRADLE_USER_HOME=/var/tmp/matt/gradle

You can set the envrionment variable in your ~/.profile file or similar to make it persistent.

Other articles

Resolving JARs

Published: Sun 20 March 2016
By mafr

In java.

tags: java python

Sometimes it's useful to check whether a local JAR file is available from Maven Central, for example when converting an old build system to Maven. In many old systems, JARs aren't named consistently and versioning info isn't available. Fortunately, Maven Central has a search interface that supports lookup by a …
read more
Preventing Cascading Failure

Published: Sun 28 June 2015
By mafr

In best practices.

tags: distributed systems java networking

With the advent of reactive programming and frameworks like Netflix' Hystrix, classic stability patterns like Nygard's Circuit Breaker Pattern have entered mainstream software development. The circuit breaker is used inside your clients to cut the connection to a collaborating system (the server) once you notice the server doesn't answer in …
read more
Hudson vs. Jenkins Revisited

Published: Tue 27 December 2011
By mafr

In tools.

tags: build systems java maven opinion

When the Hudson/Jenkins fork was announced earlier this year, the case seemed pretty clear. There were heroes from the Open Source community, among them Hudson's original author, and there was everybody's favorite villain, Oracle. Back in February, I would have chosen Jenkins without a second thought. Now, almost a …
read more
Good API Design

Published: Tue 01 May 2007
By mafr

In best practices.

tags: java quality

Recently I discovered an interesting video for all of us aspiring software architects on Google Video. As part of the "Google Tech Talks" series, Joshua Bloch talks about "How to Design a Good API and Why it Matters". Being one of the main architects of Java (among others, he designed …
read more

Other articles

social