What i need is that i can say in the parent pom of my git repo (and i have about 10 repo's that will build 1 product)
I don't want to wipe everytime, beause then i need to build all the repo's constantly, that is horrible and would take quite some time (i only want to build repo's that are changed an then trigger out dependency jobs in jenkins to also build)
I now can work by adding that specific version in all of the manifest, so this stuff:
On master branch:
On dev branch:
and also the feature.xml has fixed versions.
But tycho should really find a way to be able to do what a local eclipse workspace product build also can do.
I think that can only be done if tycho would use the normal dependencies tag of maven, where i can say in a parent pom, IF you resolve foo.core then THIS is the version you need to get
Because if i can do this in a parent pom i only have to do it in 1 place not in many many manifest of all the plugins in that git repo.
I still don't see how all these other solutions would work, because on our jenkins i have multply branches and all those branches have multiply git repo's and they are all building when ever they want and see changes so many of them can build at the same time...
So clearing out stuff i don't see how that would help.
Maybe a Nexus setup could help that all branches had there own p2 repo where they put stuff in and get from there? and all the parent poms of a branch have a specific p2 repo that they include to get the build artifacts of the other git repo's
Is there a good documentation how to set this up and how to use this?
Because in the end you really want to have feature builds also, so i can say to jenkinks quickly build and test a product that is build from these repo's with that branch and those repo's with that feature branch (not all repo's are touched by this feature only part)
This is really easy to do in a workspace like setup but in tycho this is just very hard if not quite impossible to do quickly
In my local eclipse environment i just branch 1 or 2 git repo's (that i know will change) keep the rest to "branchX" and then do the changes and commit, then with P2 export that we had i could build exactly that product in no time...
If i could just change parent poms of a git repo to fix dependencies, i could just also branch all the git repo's (like the one with the product/feature file) and change only the parent pom in that one to use the version of the feature branch of the others..