Bug 280489 - No specific notice sent for parse error
Summary: No specific notice sent for parse error
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-16 14:29 EDT by David Williams CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:

Attachments
console log from URL (26.82 KB, text/html)
2009-06-16 14:35 EDT, David Williams CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2009-06-16 14:29:18 EDT 
Or, IllegalArgumentError, technically. 

In a build such as the following, 

https://build.eclipse.org/hudson/job/galileo.runBuckyBuild/539/console

a bad error in the version number makes the version invalid, but no specific notice is sent to the offending team ... presumably because not all Exceptions are caught in that section of code. 

I think I've seen this or similar thing a few times ... maybe IllegalArgumentError should be caught too .. or, the version number checked for validity, before being turned over to P2?
Comment 1 David Williams CLA 2009-06-16 14:35:18 EDT 
Created attachment 139336 [details]
console log from URL

Since the URL won't be valid after a few days, thought I'd attach a "hard copy" of the console log for the long term.