| Summary: | Bundle Editor version value should handle invalid version format | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | UI | Assignee: | Curtis Windatt <curtis.windatt.public> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtis.windatt.public |
| Version: | 3.7 | ||
| Target Milestone: | 3.7 M7 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Olivier Thomann
To get it, you need the maximum version range to be empty. If there is a maximum version range, the error is properly reported. Fixed in HEAD. Thanks! This is not the bug I am looking for... Fixed in HEAD. See BundleFragment.java. We just need to catch an illegal argument exception when creating a version range to try to clean up the provided version. In most places where we work with version ranges, we catch number format exceptions. The OSGi class does not specify when it will return which exception, so there may be other places in PDE that this could cause a problem. Every where I tried messing with things though, it seemed to handle it ok. Verified in I20110424-2000 |