| Summary: | problem with core.resources bundle in I20110124-0916 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kim Moir <kim.moir> | ||||
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | blocker | ||||||
| Priority: | P3 | CC: | dj.houghton, john.arthorne, pwebster, Szymon.Brandys | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Kim Moir
Created attachment 187454 [details]
log
Not sure if this is an osgi issue or core.resources. There was only one changed released between I20110118-0800 which was good and now. It is Bug 330320. It appears the org.eclipse.core.resources bundle from that build was compiled against binaries for org.eclipse.equinox.preferences from an earlier build. When you restarted the build for our modified input, was it a clean restart? If the qualifier on the core.resources bundle didn't change, the same bundle would be included in the next build because it exists in a child repo of an earlier build. The core.resources bundle needs to be retagged. I'll investigate why it was pushed to the repo if it had a compile error. This shouldn't happen. I've retagged org.eclipse.core.resources for a new build. Kim is looking into why a bundle with compile errors was published to the repo. Closing. verified. |