Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 68047

Summary:	[osgi] Error in Version number should be report more details
Product:	[Eclipse Project] Equinox	Reporter:	Pascal Rapicault <pascal>
Component:	Framework	Assignee:	Thomas Watson <tjwatson>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Pascal Rapicault

2004-06-21 13:50:55 EDT

RC3.
I had a bogus version number: 3.0.qualifier.
When it has been parsed I received a IllegalArgumentException like attached
below. This is interesting however it would have been great if the bogus value
could have been displayed.

java.lang.IllegalArgumentException: Invalid micro
	at org.eclipse.osgi.service.resolver.Version.parseVersion(Version.java:242)
	at org.eclipse.osgi.service.resolver.Version.<init>(Version.java:175)
	at org.eclipse.osgi.service.resolver.Version.<init>(Version.java:150)
	at

Comment 1 Pascal Rapicault

2005-01-14 10:20:59 EST

In the layering branch.
The version class should catch the number format exception to produce a better
message. The current one is not helpful at all.

Comment 2 Pascal Rapicault

2006-04-05 11:09:18 EDT

This bug is now invalid since now the resolver uses the Version class from org.osgi.framework.