| Summary: | PDE env/descriptions missing from repository | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | Releng | Assignee: | Kim Moir <kim.moir> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, david_williams, john.arthorne, kim.moir, nboldt, remy.suen |
| Version: | 4.1 | Flags: | john.arthorne:
pmc_approved+
|
| Target Milestone: | 3.7.2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Paul Webster
Yes, the build breaks if I build them so I disabled them temporarily....will fix when I have time :-) Just a data point.. this same failure starting happening in the Indigo maintenance stream build as of M20111130-0800. That might help isolate the cause. reminder ... this is still missing from Indigo SR2 (and Juno) ... but, SR2 is about done ... and think this new one has "Java 7" definitions in it? (In reply to comment #3) > reminder ... this is still missing from Indigo SR2 (and Juno) ... but, SR2 is > about done ... and think this new one has "Java 7" definitions in it? Oh, and to be clear ... I mean "missing from b3aggrcon file, hence missing from common repo. (I've no idea if "in your build" or not :) No, I don't know how to fix this and neither do the pde api committers. Will run another test build and try to debug why this is happening. It's very frustrating. This has been released in the 3.8 stream builds. I ran a test build in the 3.7.x stream and this worked as well. I'm not sure why this had so many problems before and would not resolve. Olivier and I looked at it in detail before and couldn't figure out what was happening but the issue seems to have resolved itself :-) Requesting PMC approval to include this fix in 3.7.2 RC4 (In reply to comment #6) > Requesting PMC approval to include this fix in 3.7.2 RC4 What is the fix exactly? Just re-including them in the build? Thanks John. Fix is in 3.7.x branch as well. *** Bug 370643 has been marked as a duplicate of this bug. *** Verified in M20120208-0800 and I20120207-0800. (In reply to comment #11) > Verified in M20120208-0800 and I20120207-0800. I've also verified this now gets "pulled into" common repo as expected, at the about to be SR2 release, .../releases/maintenance (Actually, just gets pulled into content metadata ... the artifact itself is referenced indirectly via composite artifact repo.) *** Bug 341569 has been marked as a duplicate of this bug. *** |