| Summary: | Bad site.xml == cryptic failure building site - could the error message reflect the fixable problem? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Nick Boldt <nboldt> | ||||
| Component: | Tycho | Assignee: | Project Inbox <tycho-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | P3 | CC: | mistria | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Nick Boldt
Created attachment 204704 [details]
snippet of log showing failure as reported w/ Tycho 0.13.0
What is the behaviour if you use eclipse-repository instead of eclipse-update-site? (Make sure to rename your site.xml to category.xml when switching to eclipse-repository). (In reply to comment #2) > What is the behaviour if you use eclipse-repository instead of > eclipse-update-site? (Make sure to rename your site.xml to category.xml when > switching to eclipse-repository). The error message looks good in case of eclipse-repository. To be honest: eclipse-update-site is pretty close to being deprecated (see bug 342876), so I don't believe that anyone will still work on this problem. eclipse-update-site and site.xml have been deprecated for a long time, no effort will be spent here. |