Community
Participate
Working Groups
As discussed during eclipsecon 2011, we want to move eclipse rcp packaging concerns to new eclipse-product project type. I've started to collect requirements and ideas in http://wiki.eclipse.org/Tycho/Split_eclipse_repository_and_product_packaging_types#eclipse-repository_user_stories
There is also a page in the old wiki with a pretty detailed plan of how the current functionality shall be split between the two packaging type: https://docs.sonatype.org/display/TYCHO/Discussion+on+eclipse-repository+packaging+type+clean-up
I'll start working on this by refactoring the output format of the publishers used for eclipse-repository. The plan is to also use the p2content.xml/p2artifacts.xml format produced in other module types. With this step done, it should be possible to reference the product IUs created in one module from another module.
(In reply to comment #2) > I'll start working on this by refactoring the output format of the publishers > used for eclipse-repository. I have a first version of this change working. It is not fully polished yet, so it is currently only available here [1]. I doubt that I'll have eclipse-product ready for 0.14, so I'm undecided if the changes from the branch should already go into master. Several refactorings I did on the way, however, are integrated (c57225a and predecessors). [1] https://github.com/oberlies/tycho/tree/bug348586_eclipse_product
Please commit your changes to the main tycho source tree when you feel they are ready. There is no real need to let the code rot on some branch somewhere. Besides, even if you won't have the time to finish repository/product split for 0.14, other committers will be able to work on the split when the code is part of the main source tree, or at least on a branch in the canonical git repository.
(In reply to comment #4) > Please commit your changes to the main tycho source tree when you feel they are > ready. There is no real need to let the code rot on some branch somewhere. Sorry, I only just managed to round off the last changes from the github branch and to integrate them [1]. eclipse-repository now also publishes to a p2content/p2artifacts.xml backed p2 repository in the target folder. Before continuing here, I'll need to address more pressing issues (in particular bug 372780) first. [1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=2f1af6211b870c5392e7400c479c09fdb07fed8e
I think the use-case described in bug 397100 depend on this issue. It tries to create an Eclipse e4 application, and then use it in surefire configuration to run tests on it. However, the product is not visible from any other part of the build (there is no IU for it), so it cannot be used to run tests.
There is no strong use-case making such change necessary.
