| Re: [tycho-user] Tycho-Surefire guessing the Test Framework |
|
I like this debate ;) On 05/15/2012 02:10 PM, X Shel wrote: In a development phase, an eclipse plugin developper should only rely on PDE tools to run its tests or to validate its mofidications.If you are in a "continuous" approach, there is no line between development phase and build phase. Both perform simultaneously. Why do you say an Eclipse plugin developer should *only* rely on PDE tools, and as a consequence should not run a "mvn install" ? "mvn install" guarantees much more stuff that Right-Click > Run As... > JUnit plugin tests. It guarantees more comformance to OSGi (it's pretty easy to forget a critical entry in build.properties and get a test working in PDE; this error is not tolerated by Tycho), and it guarantees the build won't break because of one of his change. PDE does not guarantee that. It's a matter of habits, but developers should really run "mvn install" when they have a pom, it does not cost a lot of time now but will save a lot of time later trying to debug it in CI build. As i understand it, Eclipse PDE internally use ant generated scripts to build plugins. Those scripts are generated using configuration files such as build.properties and others. I think PDE/Build uses Ant scripts, but PDE tooling in IDE relies on internal builders of JDT to generate a classpath from MANIFEST.MF and build continuously. build.properties is ignored in IDE, it can lead to errors that are not detected in Eclipse. I can see a use case that i've recently encourter, migrating a buckminster-based build process into a tycho-based one, with sources only accessible in a readonly mode.Then the solution would probably be to avoid readonly mode ;) Most IT problems can be solved by removing constraints. |