Bug 747718

Summary: Latest SOA plugins have invalid plugin versions
Product: [Other] RHQ Project Reporter: Charles Crouch <ccrouch>
Component: PluginsAssignee: Len DiMaggio <ldimaggi>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 4.2CC: hbrock, hrupp, jcoleman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-04 05:00:06 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Charles Crouch 2011-10-20 16:30:01 EDT
If you open the META-INF/rhq-plugin.xml files inside the latest SOA plugins


You will see the version property specified in the plugin descriptor is "SOA-5.2.0". This does not match the OSGI versioning scheme we use for plugin versions, described here: http://www.osgi.org/javadoc/r4v43/org/osgi/framework/Version.html#Version%28java.lang.String%29

The consequence of this invalid plugin version is that it breaks version comparisons, e.g. if you compare "2.0.0"  with "SOA-5.2.0" then "2.0.0" will be determined to be greater, i.e. the more recent version

The solution is to drop the "SOA-" portion from the version string.

Going forward we're planning to make our plugin deployment rules tighter so you won't even be able to deploy plugins with bad versions strings. This is covered in  https://bugzilla.redhat.com/show_bug.cgi?id=747702
Comment 1 Julian Coleman 2011-10-21 13:03:06 EDT
Resolved with revision 658 of:


Commit message:

  Remove the "SOA-" prefix from the ESB JON plugin version.
Comment 2 Heiko W. Rupp 2013-09-04 05:00:06 EDT
Closing as outdated.