Hi, I'm seeing more and more frequently in my workbench errors such as "Project has only main sources but depends on project 'org.eclipse.text.tests' which has only test sources." which prevents from developing as JDT refuses to build in such case. That was implemented in https://bugs.eclipse.org/bugs/show_bug.cgi?id=539998 and made more frequent as more and more bundles added test information in there .classpath. I think overall, this practice is a bad idea for Eclipse plugin development and for Platform, because 1. it's "contaminating": changing it requires downstream consumers to also act on their .classpath to get things working again 2. it's adding no value in the traditional plugin development workflow 3. it can even cause troubles now that support for test folders in Plugins can be interpreted differently by PDE or Tycho (just like tests in Maven world).
I think we should act on fixing those .classpath and emit a rule to not use those "test" metadata on test bundles. Also, we should probably make PDE *not* add those metadata for plugins by default. There would be less trouble and no loss as far as I know. What do you think? -- Mickael Istria Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
