Re: [tycho-user] [Tycho Users] problems with the generate-poms target

["Oberlies, Tobias" <tobias.oberlies@xxxxxxx>]

I think it is a good idea to have generate-poms do as much as possible of the project setup. However I have two questions about your concrete proposal:

1) What do you need to configure on the maven-osgi-test-plugin? Tests are automatically executed if the packaging type is eclipse-test-plugin.

2) In all projects I use, the .target file is contained in a separate Eclipse project. Do you have any experience with the Tycho build if the .target file is contained in any of the source projects? Where do you usually store the .target file?

Regards
Tobias

P.S.: Please use the new mailing list tycho-user@xxxxxxxxxxx to continue this discussion and for future questions.


> -----Original Message-----
> From: tychotychonofuba [mailto:bonnier.vincent@xxxxxxxxx]
> Sent: 18 April 2011 18:23
> To: tycho-users@xxxxxxxxxxxxxxxxxx
> Subject: [Tycho Users] problems with the generate-poms target
> 
> The target generate-poms can produce parent pom.xml & poms for module and
> it
> works fine (now ) for me.
> But I want to add in the parent pom 2 plugin's references :
> target-platform-configuration &  maven-osgi-test-plugin.
> 
> Goal of my project is setting up a transparent headless automated build
> with
> Hudson/Jenkins & Maven/tycho (so developpers will not have to know what is
> a
> pom file, or what is tycho.).
> 
> It's almost done for now (the developpers doesn't know what is tycho), but
> i
> still need to modify the parent pom after its generation.
> 
> Is there a way for generate-poms target to add both plugins reference
> (target-platform-configuration and maven-osgi-test-plugin) when i generate
> all poms ?
> If no, do you have a workaround in mind ?
> 
> In my opinion, a strengh of tycho is we can keep the same workflow as
> before
> (eclipse, manifest first approach) and nobody have to know maven and pom
> files.
> 
> So an interesting feature for Tycho could be to have maven-osgi-test-
> plugin
> reference added as soon as a testbundle project is found in the workspace,
> and the target-platform-configuration reference added as soon as a .target
> file is found, doest it makes sense ?