[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-planning-council] Fragility of the XML project plan
- From: "CLONINGER ERIC-DCP874" <ericc@xxxxxxxxxxxx>
- Date: Fri, 16 Jan 2009 14:08:14 -0500
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acl4DcgFNZFTN4TSQMS8LNEGrKXUOA==
- Thread-topic: Fragility of the XML project plan
I made some changes
to the my XML project plan this morning based on our recent release.
I ran the
validator in Eclipse Ganymede and it showed no problems.
When I uploaded the
file and it became live a few minutes later, my project plan would no longer
This isn't the first time this has happened, and I remembered that Firefox has a
better validator than Eclipse. I loaded the XML into Firefox and it showed
that the problem was an unmatched paragraph end (</p>) element in one
of the sections (cut/paste error) text. Removing the extra element and
uploading solved the problem. I accept full responsibility for breaking my project plan. It
was my edit and upload that caused the problem. I will make certain to use
Firefox to validate my XML instead of Eclipse in the future.
thoughts come to mind...
- Does the XML
renderer on eclipse.org understand the difference in severity between an
unmatched paragraph element and completely malformed XML? I'm not an XML guru,
but I have more than a passing familiarity. I would think the parser/renderer
could be a little more lenient on non-catastrophic errors. At least give an
error message in the output instead of just a blank frame.
- If Firefox can find
the error, shouldn't we have the same ability in
Sr. Product Manager, MOTODEV
Eclipse Tools for Mobile
Linux Project Lead