Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Build is stuck

Open
#2 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start by reproducing the example build with Gradle 4.0.1 and Java 8, using the reported configuration output as the first diagnostic point. Inspect the example's build configuration and the p2AsMaven initialization step to determine why configuration stops at 14% without network activity. Done means the cause is identified and the example either completes or clearly reports the required fix.

Written by the indexing model from the issue text.

Description

question

Hi

i try to run this example. I use Gradle 4.0.1 and java 8 u131

Configure project :target.p2
p2AsMaven eclipse-deps is dirty.
Initalizing maven group eclipse-deps from p2
Only needs to be done once, future builds will be much faster
p2AsMaven eclipse-deps installing from p2
Buildfile: <...>\Temp\goomph-ant-build8459310540695597019.xml
[p2.mirror] SLF4J: Class path contains multiple SLF4J bindings.
[p2.mirror] SLF4J: Found binding in [jar:file:/<...>/.gradle/caches/4.0.1/generated-gradle-jars/gradle-api-4
.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[p2.mirror] SLF4J: Found binding in [jar:file:/C:/Gradle/lib/gradle-logging-4.0.1.jar!/org/slf4j/impl/StaticLoggerBinder
.class]
[p2.mirror] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
[p2.mirror] SLF4J: Actual binding is of type [org.gradle.internal.logging.slf4j.OutputEventListenerBackedLoggerContext]
<=------------> 14% CONFIGURING [2m 26s]
root project

This seems to hang, it tried to run it for several minutes. No network activity either.

Dominant language
Java
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

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/goomph-eclipse-plugin

All issues in diffplug/goomph-eclipse-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.