Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] [platform-dev] main vs test source causing annoyance

Hi Mickael, 
 
I've never seen such errors and I have most of SDK with tests in my workspace.
Also in SDK we have test and non-test bundles, and do not mix test and production code in one project.
Could you provide a concrete example of such error with explanation what and where is broken / wrong configured / how it can be improved?
Also I'm not sure PDE adds something to metadata to enforce this warning.
 
Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov
 
 
Gesendet: Freitag, 28. Januar 2022 um 09:21 Uhr
Von: "Mickael Istria" <mistria@xxxxxxxxxx>
An: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>, "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Betreff: [platform-dev] main vs test source causing annoyance
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 developer, for Red Hat Developers
_______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Back to the top