-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move equo caches into build / build tool directory #1687
Comments
The problem in my case is that |
Fixed in |
Unfortunately, this doesn't seem to have the desired effect. Now I'm getting
|
What if the Gradle/Maven plugin set |
Interesting! What system is this running on? I'm confused by the persistent Can you add Also, it is strange that |
It's running in an
Sure:
It isn't. It's returning |
Shouldn't we rather do it the other way around? I.e. check for |
Maybe |
Yes, I think that's the problem. I think that both suggestions above should fix that problem and I prefer the latter one. |
I tried adding dev.equo.solstice.p2.CacheLocations.override_p2data = gradle.gradleUserHomeDir.toPath().resolve("caches/p2-data").toFile();` to by build. That fixes the exception, however, now I get
|
Oh, I guess that's a forked process that has its own |
I just took another hack at it published in |
Looks promising, thanks! |
@nedtwigg, still not working. I added a version override to my build, but I get the same error as in #1687 (comment):
Not sure what's happening. It looks as if I still think it would be best if the Gradle plugin set the CacheLocations overrides since it knows where its user home is. |
In mvn world, the local reposirory can be configured through I also have related issues by deploying Spotless to AWS Lambda, as |
I have the same problem. In a CI environment building in a docker container I would like to set the Maven repository directory to point inside the Jenkins workspace. The problem is simple to reproduce. I have a simple groovy/greclipse spotless setup using version 2.41.1. Make the ~/.m2 directory unwritable:
I could work around the problem with (although it seems strange to a Maven user):
I would like spotless to honor the
|
The move to equo for the Eclipse-based formatters causes issues in out CI build. See #1524 (comment)
The problem is, that the plugin tries to write the equo cache into a directory that's not writable/resolvable.
I suggest moving the cache into the
${user.home}/.m2
/GRADLE_USER_HOME
directories or into the project build directory.See also #1669 (comment)
The text was updated successfully, but these errors were encountered: