Bug 747702 - do not accept plugins that have invalid version strings
do not accept plugins that have invalid version strings
Status: NEW
Product: RHQ Project
Classification: Other
Component: Plugin Container (Show other bugs)
4.2
Unspecified Unspecified
medium Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-20 16:03 EDT by John Mazzitelli
Modified: 2011-10-20 16:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description John Mazzitelli 2011-10-20 16:03:11 EDT
We should not allow plugins to be deployable if they have invalid version strings (that is, does not follow the OSGi rules for version strings).

For example, if I already deployed a plugin with version "2.0.0" and I later deploy an updated plugin with version "ABC-6.0.0", that "ABC-6.0.0" version string is not valid OSGi version format and our code will assume 2.0.0 is after ABC-6.0.0 (see ComparableVersion class).

OSGi version syntax is:

version ::= major('.'minor('.'micro('.'qualifier)?)?)?
major ::= digit+
minor ::= digit+
micro ::= digit+
qualifier ::= (alpha|digit|'_'|'-')+
digit ::= [0..9]
alpha ::= [a..zA..Z]

Note You need to log in before you can comment on or make changes to this bug.