Re: [tycho-user] Tycho-Surefire guessing the Test Framework

[Hervé Esteguet <hesteguet@xxxxxxxxxxxxxxxx>]

> What is the gain in separating? 

- We avoid polluting source with maven metadata. Tycho is not yet the native method used by eclipse to build bundles from the workbench. When it will be so, the presence of the pom.xml into a plugin source will be justified.

- The releng engineer is not always allowed to modify the source repository which can be of different sources and natures. In fact the project could depends on others projects in which you just have a readonly access.

> Looks like it makes things more difficult

- Tycho make this approach easier, in most case the modification of the pom parent generated by tycho will suffice to configure the whole build process (an XSLT transformation do the trick). There are small cases like the original subject of this thread which complicated things.

----- Original Message -----
From: "Mickael Istria" <mistria@xxxxxxxxxx>
To: "Tycho user list" <tycho-user@xxxxxxxxxxx>
Sent: Mardi 15 Mai 2012 12:12:37
Subject: Re: [tycho-user] Tycho-Surefire guessing the Test Framework


On 05/15/2012 11:56 AM, Hervé Esteguet wrote: 

In our dev team we separate releng concerns from dev ones. Sounds like a bad idea to separate them. They are tightly coupled. Code affects releng, releng affects code. You cannot isolate them. 



Our idea is that, it's not the same person which is responsible for the development and for the release engineering. Ok, but IMHO, the guy doing release engineering is part of the dev team, and should be allowed to commit poms into bundles. 



The releng engineer maintains a project which inject tycho configuration during the build process on CI. By doing so we separate eclipse bundle development from maven considerations. 

-- 
Mickael Istria 
Eclipse developer at JBoss, by Red Hat 
My blog - My Tweets 
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user