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

[vincent bonnier <bonnier.vincent@xxxxxxxxx>]

Hi Tobbias. 

You was right, it didn't need the step 5).
I was naming my test bundle **.test, i renamed them into **.tests (with
 an 's' at the end) and the maven-test-plugin reference is now added in 
the effective pom. Tycho doesn't recognize the .test (without 's') 
extension.

So now, the maven-osgi-test-plugin is added, and the packaging type for test bundles is eclipse-test-plugin 

For the second part :  
Finaly i developped a small java program in order to customize the 
parent pom. I call it from an ant script. It add the helios repository 
tag,  and target-platform-configuration section and another submodule 
with the target platform. 

So now my workflow looks like that (if someone is looking for the same project). 
1) checkout psf files and .target file from the svn 
2) Use Ant4eclipse to build workspace from psf files.
2) generate poms
3) customize poms (adding helios repository, target-platform-configuration and the module with the .target)
3)  build with Maven/tycho the sources and execute tests. 

The main advantage of this approach is the fact that there is no changes on the developer side 
(everybody works like yesterday using eclipse, the .psf files, the 
.target file etc. and nobody need to know anything around maven or 
tycho). 

Everything is ok for me. Thanks for all. In the future, may be 
it could be great not to have to customise pom like i do (maybe adding 
repository reference and target-platform-configuration section as soon 
as a .target file is found in the workspace).