Skip to content
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

Gradle build error in gitpod #56

Closed
tch1001 opened this issue Feb 3, 2022 · 1 comment
Closed

Gradle build error in gitpod #56

tch1001 opened this issue Feb 3, 2022 · 1 comment

Comments

@tch1001
Copy link

tch1001 commented Feb 3, 2022

There is a gradle build error when opening in gitpod, as well as when compiling locally (the local compilation may be my own fault but the gitpod one doesn't work either). Here are the logs from gitpod. Thank you

Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 1m 22s
30 actionable tasks: 30 executed
Picked up JAVA_TOOL_OPTIONS:  -Xmx2576m
Registering ELK version 0.7.1.
Registering ELK version 0.7.0.
Registering ELK version 0.6.1.
Registering ELK version 0.6.0.
Registering ELK version 0.5.0.
Registering ELK version 0.4.1.
Registering ELK version 0.4.0.
Registering ELK version 0.3.0.

FAILURE: Build failed with an exception.

* Where:
Build file '/workspace/elk-live/server/elkgraph-web/build/elk-layout-versions/0.3.0/build.gradle' line: 17

* What went wrong:
A problem occurred evaluating project ':0.3.0'.
> Server returned HTTP response code: 504 for URL: https://search.maven.org/solrsearch/select?q=g:%22org.eclipse.elk%22+AND+a:%22org.eclipse.elk.alg.force%22+AND+v:%220.3.0%22&core=gav&wt=json

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 1s
gitpod /workspace/elk-live/server (master) $ 
@Eddykasp
Copy link
Contributor

closing this issue as it does not appear to be broken currently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants