Community
Participate
Working Groups
Being a Eclipse/Java newbie and been offered a Cheat Sheets for Hello World, I went directly to it, only to discover that it's not a nice experience for a new user. Some items are incorrectly descibed (like the first step: "Window > Open Perspective > Java" as there's no such a thing). Some steps give warnings ("The use of the default package is discouraged.",...) And finally, when you try to run the Java application following the steps provided, you get errors: "Error occurred during initialization of boot layer java.lang.module.FindException: Error reading module: D:\eclipse-workspace\HelloWorld\bin Caused by: java.lang.module.InvalidModuleDescriptorException: HelloWorld.class found in top-level directory (unnamed package not allowed in module)" I know this is very easy to solve for someone with a entry-level knowledge, but considering that this Cheat Sheet is oriented to the newcomers, is IMPERATIVE to re-write it so the first experience is flawless!
Lars, something for the Hamburg hackathon?
I have just been through it with 4.15M3 and it was ok, in terms of following along and matching steps. I would definitely agree with Fernando that random warnings do sound ominous when you are starting to learn. A note in the cheat sheet would go a long way to making the new user feel confident that they are going in the right direction.
Noopur, where do I find the JDT cheatsheets?
(In reply to Lars Vogel from comment #3) > Noopur, where do I find the JDT cheatsheets? https://git.eclipse.org/c/jdt/eclipse.jdt.git/ - This repo has JDT cheatsheets.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Please create PR for Github if you still thinkk it is relevent.
