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

AspectJ Internal Error: Unsupported class file major version 61 #19

Closed
ptziegler opened this issue Apr 27, 2023 · 5 comments · Fixed by #24
Closed

AspectJ Internal Error: Unsupported class file major version 61 #19

ptziegler opened this issue Apr 27, 2023 · 5 comments · Fixed by #24

Comments

@ptziegler
Copy link
Contributor

I'm currently preparing our product for the upcoming Eclipse release, which requires at least Java 17. RCPTT is currently using AspectJ 1.9.7, which only supports Java versions up to 15/16, making it impossible to launch our application.

This version of AspectJ is contributed by AJDT up to version 421. RCPTT is currently still using 410. Is it possible to update this dependency?

@basilevs
Copy link
Contributor

basilevs commented Jun 30, 2023

Sure, we accept PRs. AFAIK, the dependency is fetched in

<url>https://download.eclipse.org/tools/ajdt/410/dev/update/ajdt-e410-2.2.4.202103162301</url>
and
<url>http://download.eclipse.org/tools/ajdt/48/dev/update</url>
but I may be wrong.

@ptziegler
Copy link
Contributor Author

The problem seems to already be solved as part of #2, so I'm not sure if it makes sense to create a separate pull request with effectively the same change.
I tried building/testing the branch locally and so far without any issues. Is there anything else holding back the branch from being merged?

@benken-parasoft
Copy link
Contributor

benken-parasoft commented Aug 4, 2023

Is there anything else holding back the branch from being merged?

Any update? This is blocking us from testing AUT with Eclipse 4.28 and Java 17.

@basilevs
Copy link
Contributor

basilevs commented Aug 4, 2023

The builds in #2 are failing for reasons unrelated to the change, so we can't merge that.

@basilevs
Copy link
Contributor

I've recreated #2 as #24 in hope, that build failures are caused by Jenkins sticky state.

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

Successfully merging a pull request may close this issue.

3 participants