Utilities Failing to Import through Spring Tool Suite
See original GitHub issueDescription
As a Core Developer Apprentice for the Ethereum Foundation, I’m using the Teku build as reference in order to build a prototype for the Altair Minimal Light Client (https://github.com/jeyakatsa/Altair----Minimal-Light-Client-Prototype). Yet, I’m having issues in regards to the utilities needed to be imported in order for the packages (and classes/interfaces within the build) to be error free…
Steps to Reproduce (Bug)
- Git Pull Teku folder into OS
- Open Spring Tool Suite 4
- Go to [File] -> [Open Projects From File System] and choose Teku folder from files
Expected behavior: No Errors packages, classes and interfaces
Actual behavior: Errors on all packages, classes and interfaces.
Image Reference
Frequency: All the time
Versions
- Software version: [
Unsure... Forked and Pulled the Teku Repo on Wednesday 9/29/21.
] - Java version: [
jdk-15.0.1.9-hotspot
] - OS Name & Version: [
Windows 10
] - Virtual Machine software & version: [
Spring Tool Suite 4, Version: 4.7, Release: 2020
]
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
java - Error in some import statements in my "Simple Spring ...
I am using Spring Tool Suite (STS) Version: 3.1.0.RELEASE. I have created a "Spring Template Project" as "Simple Spring Hibernate Utility ...
Read more >Can't import Spring Tool Suite 4.10 from Eclipse Market Place
Tried to import STS from Thrid Party Libs -> Elciplse market place. This is in the log: INFO: Active connection settings changed to ......
Read more >Newcomers » Import not accessible - Eclipse Community Forums
I am finding with nearly any package I am importing I am always coming across the "X is not accessible" even when going...
Read more >@UtilityClass maven build fails when static importing a public ...
When I run the code from eclipse everything works fine. ... The fix to the problem is quite simple just explicitly specify in...
Read more >Intellij IDEA cannot resolve any import statement
It happend twice when I imported Eclipse RCP project. Once it fails with Eclipse RCP project it affects whole intellij idea and it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not at all familiar with spring tools suite but it looks like it’s built on Eclipse. It looks like Eclipse is having issues again because it doesn’t separate test, test support and production code trees in the same way gradle does so it hits a dependency cycle where gradle and IntelliJ have no issues.
Eclipse isn’t giving me very useful error messages to point out where it thinks the cycle is either unfortunately. We’ll have to do some further analysis to work it out and then how to restructure things to make Eclipse happy.
Thanks for raising. I’m assuming that you’re importing the rest api definition?
There’s been a couple of reports of specific issues due to automated importing of the rest api, and previously I’ve suggested importing the standard api which is written by hand… The standard api can be found here. Admittedly ‘teku specific’ api’s are missing from that definition, but all of the key api’s are defined : https://ethereum.github.io/beacon-APIs/
Last time I checked it was difficult to fix due to external dependencies of several libraries, I’ll schedule some time to see if it’s in a state to attempt to resolve yet…