Community
Participate
Working Groups
I use the director to build either the 3.6 eclipse SDK or the 4.0 eclipse SDK, usually with the standard SDKProfile. I need to be able to create 2 runnable profiles from the same install: ex: SDKProfile for 3.6 with org.eclipse.ui.workbench 3.6.0 and SDKProfile40 for 4.0 with org.eclipse.ui.workbench 3.100.0 Almost all of the other bundles are the same between the 2 profiles (and so presumably can be in the single bundle pool). Each profile contains a different version of the top level product, org.eclipse.sdk.ide. Profiles are not runnable by themselves, but I was not able to find a way to generate different eclipse/<configuration> directories to contain the different config.ini files (with potentially different eclipse.p2.profile=SDKProfile and other properties, like the bundles.info) The goal in this is to provide an eclipse 3.7 SDK install that can (with a slight change) launch in 4.1 with e4 + compatibility mode. PW
I would do that by using the bundle pool argument on the director application, and do two calls to create two different install folders. You would end up with eclipse/ p2/ plugins/ ... features/ ... e4/ configuration/ e3/ configuration What I'm not sure about here is whether the paths would be relative.
(In reply to comment #1) > > What I'm not sure about here is whether the paths would be relative. We found out when trying to create multiple architectures within one zip that you can get most of the way there using the pattern you describe, but you end up with absolute paths. See bug 344153, bug 344155, and bug 342156 PW
Thx for the references.
