greclipse is downloading run time dependencies to P2 repo of 138MB

Open
#2,936 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
groovy
Domain
build-system

Research direction

The issue names the Gradle Spotless plugin, the greclipse formatter, and the ~/.m2/repository/dev/equo/p2-data cache; start by tracing greclipse dependency resolution during spotless check. Compare available formatter alternatives for Groovy build.gradle files and verify whether the 138 MB runtime download can be avoided or cached; done requires a documented, supported path.

Written by the indexing model from the issue text.

Description

We upgraded to gradle spotless plugin 8 from spotless 5 and recently noticed our pipelines slowed down. Then noticed there are some dependencies being downloaded at run time for spotless check. And these are related to greclipse.

    94M ~/.m2/repository/dev/equo/p2-data/bundle-pool/download.eclipse.org--EJM2QXrlNDLw7z5SNWvx4w--clipseupdates-4.35-R-4.35-202502280140-/
    33M ~/.m2/repository/dev/equo/p2-data/bundle-pool/https-groovy.jfrog.io-artifactory-plugin--ldtmrg6m1JSts76B3o3M0Q---groovy-eclipse-integration-5.7.0-e4.35-/
    11M ~/.m2/repository/dev/equo/p2-data/nested-jars
    344K ~/.m2/repository/dev/equo/p2-data/metadata
    44K ~/.m2/repository/dev/equo/p2-data/queries

We can use internal repos and cache to speed it up. But it makes no sense for me to download 138 MB worth of deps just for formatting groovy. Is there any alternative to greclipse? We use groovy mainly for build.gradle files.

Dominant language
Java
Stars
5.7k
Forks
560
Avg merge
1d 13h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/spotless

All issues in diffplug/spotless

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.