Bugzilla – Full Text Bug Listing
| Summary: | MalformedURLException thrown by p2 on startup | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Dani Megert <daniel_megert> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer, ed, nboldt, susan |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Dani Megert
These features do actually have bogus URLs due to a PDE build bug (bug 228114). We could avoid logging the exception, but that might hide useful details when a feature has an invalid update URL. It was actually a bug that we were parsing already installed features on startup in that build. It has been fixed, and in I20080428-0800 you don't see these messages on startup. Since there is another bug for that, and a bug for the bogus URLs in the features, I'm going to close this. We should log bad URLs when we encounter them, or developers would never discover that they have invalid feature update URLs. >We should log bad URLs
>when we encounter them, or developers would never discover that they have
>invalid feature update URLs.
Agree.
*** Bug 229516 has been marked as a duplicate of this bug. *** *** Bug 231063 has been marked as a duplicate of this bug. *** Apologies for re-opening, but I don't really have anything else to hang this problem off. I have done two separate upgrades on an M6 workspace and found both to be very troublesome. On both this message was very apparent. On the second it seemed to get far worse because of some attempt to then update through an obstinate firewall without adequate access. In both cases Eclipse was started with -data pointing at the 3.4M6 workspace. The resulting Eclipse session comprised just the platform. All other components such as EMF, GEF, EMF-Query/Tranaction/Validation, OCL were missing. On the first occasion I tried about 15 combinations of partial installations to isolate a repro without success. All worked. I just complained about a lousy IU message (bug 231051) that told me nothing about what was wrong. On the second occasion, the nightmare was at least familiar though the proxy made it worse. The workaround that seemed to solve the problem each time was to perform the Eclipse installation (unzip all ZIPs to a shared directory) then start Eclipse with a fresh workspace. This works fine. With the Eclipse installation directory fully initialised, Eclipse can then be restarted with a -data pointing at a 3.4M6 workspace. So it appears that M7 is unable to initialise while using an M6 workspace. The MalformedURLException is a valid exception being logged because of features with invalid update site URLs. This exception has no other side-effects and is unrelated to your problem. I suggest entering a new bug if you are still seeing problems in the most recent builds. *** Bug 234410 has been marked as a duplicate of this bug. *** |