diffplug / diffplug/goomph-eclipse-plugin
Build is stuck
- Vorherrschende Sprache
- Java
- Sterne
- 1
- Forks
- 2
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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.
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java
- Bereich
- build-system
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100