| Summary: | [releng] S-4.1M2-201009161954 doesn't include eclipse 3.7 M2 | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer, bokowski, john.arthorne, kim.moir, Mike_Wilson |
| Version: | unspecified | ||
| Target Milestone: | 4.1 M2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Paul Webster
Things to try: 1) remove the runnable repo and force it to rebuild 2) merge the 3.7 feature.map into our short build feature.map to pick up the 3.7 features. Andrew, do the fetch factories support fetching features from a p2 repo? If I don't have to rebuild the org.eclipse.jdt feature, that would be better. PW I've deleted our M2 sites. We'll spin an M2 build after I can work on build.eclipse.org and after the 3.7 M2a. PW You can have a look at http://build.eclipse.org/eclipse/e4/build/e4/downloads/drops/4.0.0/40builds/I20100921-1710/I20100921-1710 These are test builds, but I think I've managed to fix my ECF problem and pick up the M2a I build. PW I've compared the test 4.1 build to I20100921-1024 and I20100921-1024 was consumed correctly. I'm running a tagged build based on I20100921-1024. If I20100921-1024 is promoted to M2a we'll be able to follow with the tagged build. PW |