capability with version in it as string.

[David Daniel]

I had a feature in my features.xml.  I tried to publish a capability as a
work around by adding

<capability>osgi.wiring.package;effective:=active;osgi.wiring.package="javax.validation";version="1.2"</capability>

It broke the feature code here line ~80


                Version v1 =
(!cap1.getAttributes().containsKey(PackageNamespace.CAPABILITY_VERSION_ATTRIBUTE))
                        ? Version.emptyVersion
                        : (Version)
cap1.getAttributes().get(PackageNamespace.CAPABILITY_VERSION_ATTRIBUTE);
                Version v2 =
(!cap2.getAttributes().containsKey(PackageNamespace.CAPABILITY_VERSION_ATTRIBUTE))
                        ? Version.emptyVersion
                        : (Version)
cap2.getAttributes().get(PackageNamespace.CAPABILITY_VERSION_ATTRIBUTE);

because an exception was thrown when trying to cast version="1.2" from a
string to a Version

I have since fixed my raggedy work around but wanted to let you know in
case you could think of a legitimate reason to try and pretend like their
is a bundle installed that is really not.