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

Got error after installing new LTS 2023-12 eclipse and newest vrapper version #864

Open
KhoaLee opened this issue Dec 7, 2023 · 6 comments

Comments

@KhoaLee
Copy link

KhoaLee commented Dec 7, 2023

image

@keforbes
Copy link
Contributor

keforbes commented Dec 9, 2023

Did you install from the Eclipse marketplace (from within Eclipse)? Could you try installing from the unstable update site instead? The unstable update site has newer changes, I'm curious if it'll work.
http://vrapper.sourceforge.net/update-site/unstable

@albertdev
Copy link
Member

I've seen people post this kind of stacktrace before, e.g. #841, but I think we have never really figured out why this happens.

The last comment in that issue ticket also states that they tried with the latest unstable version 0.75.

@frankbenoit
Copy link
Contributor

I interpret the stacktrace like this ....

The Genuitec tooling is installed. It is a tool that implements dark theme in Eclipse.
From the stacktrace it seems this is trying to use reflection to call "setCSSForeground" which is not existing.
I do not understand if vrapper's CLable should have it. The base class does not have it either.

@KhoaLee I propose to report a problem report at Genuitec

@frankbenoit
Copy link
Contributor

On the other hand, the vrapper CLable class mentions styling and it uses the same name as the base class to avoid e4 dependency. Is this still a concern, the e4 dependency?

@frankbenoit
Copy link
Contributor

@KhoaLee there is already https://www.genuitec.com/forums/topic/conflicts-with-vrapper/
you might give it a bump up

@albertdev
Copy link
Member

On the other hand, the vrapper CLable class mentions styling and it uses the same name as the base class to avoid e4 dependency. Is this still a concern, the e4 dependency?

If it was decided to jump to Java 17 compatibility and hence block out Eclipse 3.x versions anyway then I can't see why. Just depend on an E4 bundle which is slightly older than the latest one, otherwise people cannot use Vrapper if they're running a few Eclipse versions behind.

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

4 participants