- This topic has 5 replies, 4 voices, and was last updated 7 years, 6 months ago by
.
-
Posts
-
Hi there,
Yesterday when I closed eclipse (Luna Service Release 1a (4.4.1)) it started an update for webclipse. Since then all things Angular have disappeared. No perspective, .ts are no longer recognized. I cannot work on my Angular2 project anymore.
I know this will be the last version to support luna, but I’m not too happy to have an update forced upon me that locks me out.
Is this a known thing? Anything I could do to rectify this?
Regards,
Mirko
Mirko,
I am sorry to hear that. This was supposed to be the last update which supports Luna and further updates would not be applied to it. Looks like something went wrong with the update process itself, for which I am sorry. I hope we will be able to quickly figure out what’s wrong. Can you please share your Error Log? Open Window -> Show View -> Error Log and than click “Export log”.
Best regards,
Piotr TomiakHi Piotr,
Thanks for your reply. I attached the error log to this message. Looking forward to your reply.
Best regards,
MirkoThe good news is that the error log has the root cause – and hopefully the fix is easy for you. In short, if you run your Luna Eclipse with Java 1.8, you’ll be up and running.
It turns out one of the plugins we rely on in our Angular tooling has a 1.8 dependency and since you are running 1.7.0_75, all of the plugins in that part of the dependency graph are not starting — thus causing these features to disappear.
Would it be possible for you to switch and run with 1.8?
Cheers,
TimHi Tim,
Thanks for your quick reply. Unfortunately switching to 1.8 is not a short term solution for me. I have a number of ongoing java projects that have a 1.7 requirement. It is one of the reasons I’m still on Luna as well.
Is there any way to revert webclipse to the previous version? I have two Angular2 projects that I need to finish pretty soon.
Regards,
MirkoMirko,
Java 8 is only needed to run eclipse, not for your projects. You can start eclipse with a -vm parameter pointing to a Java 8 executable but specify a Java 7 JRE as your default JRE inside eclipse. This way, the tooling which requires Java 8 can start up but you can still use Java 7 for any projects that require it.
We’ll look at alternatives of course, but this should get you going. Let us know if you see problems with it.
