Compiler seems to include undesired projects

[Guite]

Say you have plug-in bundle named org.example.foo.bar. If you then add another plug-in named org.example.foo.bar.tests and activate Jnario for it, then the compiler is always executed in both projects - probably due to the name clash... Even if you disable the compiler in the global settings and only enable it again in the project-specific settings of the tests plug-in, it still includes both projects (creating undesired folders like docs-gen, etc.).

[sebastianbenz]

Unfortunately, I can't reproduce your problem. Jnario should never create the doc-gen folder on its own (only the xtend-gen). Could you please provide an example project that exposes the behavior.

[Guite]

During the last days I migrated some other plug-in bundles from Java to Xtend. While doing that I just noted that the docs-gen folder is created in all Xtend projects - independent of whether Jnario is used or not. As soon as the Xtend dependencies (com.google.guava, org.eclipse.xtend.lib and org.eclipse.xtext.xbase.lib) are added to the dependencies, the docs-gen folder is created as part of the build.

[sebastianbenz]

Could you please post an example project that exposes the behavior. Thanks.

[Guite]

After some experiments I now know how to reproduce it :smile:

The problem is caused by the general settings - even if the projects all have project-specific settings. Note that in both projects contained in the workspace the docs-gen folder is created.

Please see the following image of the general settings page:

A workaround is probably to reset the general settings to the default values (still have to investigate that though).

[Guite]

Solved by setting the directory names to blank value in project-specific settings.

[Guite]

https://github.com/Guite/MostGenerator/commit/b3484bbd8bea2e649ef10b4f1efb24f2d48274db

[sebastianbenz]

OK. This is definitely a bug. Thanks for the efforts.