Community
Participate
Working Groups
I switched the R4_HEAD plugins and fragments to p2IU against http://download.eclipse.org/eclipse/updates/3.6 I had to put the ECF ones back, and the jetty ones. Once that was done I got some problems with about.html copy that could probably be removed from the postFetch (it would save time to not have to compile SWT) but for now I've just reverted those parts of the map files. I was making progress in 4.0 up until I got to the generated source features vs binary plugins: Unable to generate source (org.eclipse.equinox.app.source) from binary bundle org.eclipse.equinox.app_1.3.0.v20100512. Andrew's suggestion was to use postFetch to suck them over: <ant antfile="${genericTargets}" target="fetchElement"> <property name="type" value="plugin" /> <property name="id" value="org.eclipse.equinox.app.source" /> </ant> and generate them into a map file. PW
Other suggestion: We can handcraft an IU something like this: <unit id='osgi.source' version='1.0.0'> <update id='osgi.source' range='[0.0.0,1.0.0)' severity='0'/> <requires size='1'> <required namespace='org.eclipse.equinox.p2.eclipse.type' name='source' version='1.0.0'/> </requires> </unit> stick that somewhere: ${craftedRepo} and then do a mirror from ${craftedRepo} + /updates/3.6 and that should pull in all source bundles. I dont know if that is more than we want or not <required namespace='org.eclipse.equinox.p2.eclipse.type' name='source' range='[1.0.0,1.0.0]'/>
I have a buildRepo and a master zip before it yacked on the tests. /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/workspace/builds/I201007071406/src/I20100707-1406/eclipse-master-I20100707-1406.zip I've commented out the sdk tests, see how far it gets. PW
Created attachment 173716 [details] Patch to eclipsebuilder
Created attachment 173717 [details] XML to get the source files
I've tagged the maps that work using_R3_6_v2. Now I need to revert them for the build :-) It looks like the director wasn't successful /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/workspace/builds/I201007071517 and so the zips didn't get very far. Then it died. PW
The repo generated doesn't contain any of the binary artifacts, like org.eclipse.equinox.executable_root* or org.eclipse.rcp.configuration_root. Only: org.eclipse.cvs_root_1.2.0.v20100427-7B77FKs8sF7B77TDW5CWE5 org.eclipse.equinox.server.servletbridge_root_1.0.0.v20100510-42A79oB5855K5E org.eclipse.jdt_root_3.6.0.v20100526-0800-7z8XFUJFMTfCWGoVuHImpms9H155 org.eclipse.platform_root_4.0.0.v20100627-1530-9LEiGN9FmrPcU0RUkQkw9q8tGje7KshUQME9d org.eclipse.rcp_root_4.0.0.v20100624b-9PCJFKvFuduJNUgd6Jz0TlOPLD8c org.eclipse.sdk.examples_root_3.3.0.v20100527-817fFcfFEdcVbpRlgyBRcVX PW
Andrew, can I mirror the entire .../eclipse/updates/3.6 repo into the buildRepo so it includes it in the eclipse-master-I*.zip and so it would be used for building the eclipse 4.0 SDKs? And not have it interfere with the parts I need to rebuild, like the features and product? What actually needs to be re-built to create a 4.0 SDK: 1) all of the features, since the 4.0 org.eclipse.rcp now includes org.eclipse.e4.rcp. Probably the product. 2) I actually need to build the plugins we've changed, org.eclipse.rcp, org.eclipse.platform, org.eclipse.ui.workbench (maybe one or two more) 3) the build id used needs to be the current one. Does the build generate that into the rcp.configuration binary artifacts? PW
.
