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.

Sign up for GitHub

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

Jump to bottom

error after upgrading eclipse #3659

Closed
Rob46 opened this issue Dec 11, 2021 · 10 comments
Closed

error after upgrading eclipse #3659

Rob46 opened this issue Dec 11, 2021 · 10 comments
Labels
p4 type: bug

Comments

@Rob46
Copy link

Rob46 commented Dec 11, 2021

After upgrading eclipse I am getting this error and don't know how to resolve it:

An internal error occurred during: "Initializing Java Tooling".
Cannot invoke "com.google.cloud.tools.eclipse.appengine.libraries.persistence.LibraryClasspathContainerSerializer.loadContainer(org.eclipse.jdt.core.IJavaProject, org.eclipse.core.runtime.IPath)" because "this.serializer" is null

  • Cloud Tools for Eclipse version: 1.8.5.202108061424
  • Google Cloud SDK version: 366.0.0 (non-managed)
  • Eclipse version: 4.22.0.v20211124-1800
  • OS: Windows 10 10.0
  • Java version: 17

What did you do?

What did you expect to see?

What did you see instead?
@craigmit
Copy link

craigmit commented Dec 12, 2021 •
edited
Loading

Eclipse 2021-12 has this problem. Rolling back to Eclipse 2021-09 fixes it (obviously not ideal).

@zhumin8 zhumin8 added the p3 label Dec 13, 2021
@zhumin8
Copy link
Contributor

zhumin8 commented Dec 13, 2021

@Rob46 and @craigmit, Thank you for reporting and adding extra info, we'll investigate more into this.

@vbresan
Copy link

vbresan commented Jan 13, 2022 •
edited
Loading

Any news or other workaround except rolling back to Eclipse 2021-09?

With this error it is impossible to even open an existing project.

@Shawn-in-Tokyo
Copy link

The following worked fine for me:

Eclipse Version: 2021-12 (4.22) Build id: I20211124-1800
Google Cloud Platform for Eclipse 1.8.5.202108061424
Google Cloud SDK 368.0.0

If I install Eclipse m2e - Maven support in Eclipse IDE (from the Eclipse Marketplace) then I do get the reported error that ...
An internal error occurred during: "Initializing Java Tooling".
Cannot invoke "com.google.cloud.tools.eclipse.appengine.libraries.persistence.LibraryClasspathContainerSerializer.loadContainer(org.eclipse.jdt.core.IJavaProject, org.eclipse.core.runtime.IPath)" because "this.serializer" is null

@vbresan
Copy link

vbresan commented Jan 14, 2022

Unfortunately I can not uninstall m2e as Google Cloud Platform plugin depends on it. Perhaps GCP is not compatible with the latest version of m2e?

Clipboard01

@chanseokoh
Copy link
Contributor

Please use Eclipse 2021-09 while we are working on #3661. If anyone can help fixing failures in #3661, we'd greatly appreciate it.

@Shawn-in-Tokyo
Copy link

Unfortunately I can not uninstall m2e as Google Cloud Platform plugin depends on it. Perhaps GCP is not compatible with the latest version of m2e?

Clipboard01

Eclipse EE 2021-12 will add in M2E 1.19 which is the problem. An Eclipse install of 2021-12 and then the Google Cloud Platform for Eclipse 1.8.5. will use M2E 1.18.1.20210618-2246 which works fine.

Then you can install Git, Mylyn, Eclipse Java EE Developer Tools etc to get the EE functionality. Just don't update M2E.

@chanseokoh
Copy link
Contributor

@briandealwis M2E 1.19 causing the failure while 1.18.1 is OK is an integrating report.

@vbresan
Copy link

vbresan commented Apr 19, 2022

I can confirm that the plugin is not working with eclipse 2022-03.

@chanseokoh chanseokoh mentioned this issue Jun 27, 2022
Open
zhumin8 added a commit that referenced this issue Aug 1, 2022
@zhumin8
update readme with supported Eclipse versions
7d3e834 
update readme with info to reflect that Eclipse 4.22 and later are currently not supported. Eclipse latest is currently on 4.24 now and 4.25 will come out soon.
Related issues got fired in #3659, #3660, #3678; attempts to fix in #3661 but no progress since.
Suggest adding this to readme and removing when this issue actually get fixed.
@zhumin8 zhumin8 mentioned this issue Aug 1, 2022
Merged
zhumin8 added a commit that referenced this issue Aug 1, 2022
@zhumin8
update readme with supported Eclipse versions (#3681)
2e68f65 
update readme with info to reflect that Eclipse 4.22 and later are currently not supported. Eclipse latest is currently on 4.24 now and 4.25 will come out soon.
Related issues got fired in #3659, #3660, #3678; attempts to fix in #3661 but no progress since.
Adding this to readme. Remove when this issue actually get fixed.
@lqiu96 lqiu96 added p4 and removed p3 labels Jun 26, 2023
@diegomarquezp
Copy link
Contributor

The latest supported version of CT4E is 4.21 (see #3681)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
p4 type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@Shawn-in-Tokyo @vbresan @zhumin8 @lqiu96 @chanseokoh @craigmit @diegomarquezp @Rob46