| Re: [tycho-user] Simplified product definition? |
Hi Thanks for the quick response. Actually, in my case I can “trust” the repositories as these are produced “in-house”. I actually want to use my product build as a proof/validation that several p2-repositories can be eventually combined into a running Eclipse instance, without version conflicts, etc. And I want to do this following a continuous integration like approach: every new build of a source p2 repo should trigger the product build. To (continuously) build a product is very attractive as it validates the mutual consistency of the p2 repos (= they can be installed together) and it creates a real executable instance which can be started (manually) to evaluate UI interactions induced by the combination of tools (each represented by an individual source p2 repository). Maybe I’m thinking in the wrong direction and there is a better way to produce this required running validation instance out of several p2 repositories in a continuous integration set up. I know for instance B3 Aggregator can do at least the consistency check part but there seems to be no Maven/Tycho integration … Regards Klaus From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria Hi, Question: is there a way to define my product more dynamically, so that the final feature content reflects the content of my p2 <repositories> without adapting my .product file manually? Something like an "include all features" possible in the .product file? It is not possible. Product files are file that specify the content of your product, and all those definitions are static. -- |