RFR: 8290473: update Eclipse .classpath in apps, buildSrc [v2]

[Nir Lisker]

On Mon, 1 Aug 2022 19:34:11 GMT, Andy Goryachev <angorya at openjdk.org> wrote:

>> buildSrc/.classpath line 10:
>> 
>>> 8:   <classpathentry kind="lib" exported="true" path="../build/libs/antlr-runtime-3.1.3.jar"/>
>>> 9:   <classpathentry kind="lib" exported="true" path="../build/libs/stringtemplate-3.2.jar"/>
>>> 10:   <classpathentry kind="lib" exported="true" path="../build/libs/swt-debug.jar"/>
>> 
>> Why does buildSrc need to be a project? It contains no relevant sources.
>
> It probably does not, the file was added in 2013 as a part of
> RT-31216: Ensure NetBeans development in Gradle build works [Eclipse files]
> 
> Turns out, eclipse can work with nested projects.  Shows multiple hits when looking for resources, but it does.
> 
> I've added a separate project for ColorCube app as an example, but since this PR is about making all directories to build on Eclipse, I'd rather not fix all the apps in this PR.  (I would keep ColorCube as a reference though).

Then best to remove the `buildSrc` project files.

I will look at the apps later. I think it's best to create a project per app while we are touching this point. I don't see a reason not to.

-------------

PR: https://git.openjdk.org/jfx/pull/858