Mickael Istria

> Tycho supports many aspects of .classpath already and tycho should behave as close as possible to the IDE to not have different outcomes between TychoIDE That's 1 possibility, it...

> well simply delete the .classpath and import the project and you will see that it will completely fail. Without .classpath and .project, there is usually 0 issue. The "Import...

> Only if you have a pom.xml If you don't have a pom.xml, then it's configured as a plugin project and .project/.classpath are generated. That doesn't prevent to build with...

> Just for curiosity I searched in platform code for You missed https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse-platform-parent/pom.xml#L708 , and this `bree-libs` profile is set on all CI builds. But Platform does commit .classpath and...

> To avoid generate an invalid sigurature in theses cases check the artifact classifier before checking if the jar exists in plugins/ Can you please provide detailed steps to reproduce...

> are you aware of some code in that area that might have a problem with the fact that the maven-version=1.0.0 but the bundles OSGi-version=1.0.0.201802012106 I don't remember sorry. I'd...

I like the general idea a lot, but I don't think it should be a plugin, but instead an `includeSources` flag on assemble-repository.

I just noticed https://github.com/eclipse/tycho/pull/1120 , which seems to cover this story better than initially described,

> I would need to re-implement everything that I want from surefire Can you please exmlain how adding the xvfb-maven-plugin does require to re-implement anything?

> Use xvfb-maven-plugin to set up the environment in pre/post phases of the run. As I explained I would prefer to not use this and rather go with the official...