This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 219632 - Version string for plugins needs qualifier
Summary: Version string for plugins needs qualifier
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 major (vote)
Target Milestone: ---   Edit
Assignee: Leonard Richardson CLA
QA Contact: Hubert Leung CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-20 12:52 EST by David Whiteman CLA
Modified: 2012-01-03 13:46 EST (History)
5 users (show)

See Also:


Attachments
Patch to add check for existence of .qualifier in version string (1.98 KB, patch)
2008-03-25 12:15 EDT, Leonard Richardson CLA
sadravid: iplog+
Details | Diff
Patch to ignore .source plugins (916 bytes, patch)
2008-04-15 09:13 EDT, Leonard Richardson CLA
sadravid: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David Whiteman CLA 2008-02-20 12:52:14 EST
This is a request to go through all COSMOS features and plugins to ensure the version string includes the .qualifier at the end.  I noticed that a bunch of the DC ones and the org.eclipse.cosmos.common one are versioned 1.0.0, which would cause them to just get replaced every build.
Comment 1 Ruth Lee CLA 2008-02-21 15:47:20 EST
David, can you explain the impact in practical terms for me, please? What gets replaced? Does that break anything or is this a "performance of build can be improved" item? I'm asking so that we can choose an iteration to target this to.
Comment 2 David Whiteman CLA 2008-02-21 16:04:44 EST
The issue is the fact that the file names of plugins for different builds does not change, the way they are currently configured.  So if a plugin was called plugin_1.0.jar in i8, it is also called plugin_1.0.jar in i9.  Once you install the one for i9, it would replace the i8 version of the file, and you would have no trace of the i8 version on your system in case you needed to revert.  You would also have trouble identifying what build the plugin came from.  Further, it just makes sense for them to have different names since they have different content.

When you include the .qualifier tag in your version string, it gets replaced by the unique number of the build.  So you would instead get plugin_1.0_v200802211234.jar for i9, and then perhaps plugin_1.0_v200803135234.jar in i10.  It's an easy change to make and helps us stay consistent with our other plugins and Eclipse guidelines.
Comment 3 Ruth Lee CLA 2008-02-21 16:24:51 EST
Based on David's explanation, targeting to i10. 
Comment 4 Ruth Lee CLA 2008-03-07 11:33:53 EST
Assigning to Leonard as per Saurabh's/Jack's request.
Comment 5 Leonard Richardson CLA 2008-03-25 12:15:42 EDT
Created attachment 93418 [details]
Patch to add check for existence of .qualifier in version string

This patch provides a check in the build for the existence of the .qualifier in the version string.
Comment 6 Saurabh Dravid CLA 2008-03-28 10:36:07 EDT
Following plugins needs to have qualifier in version string.

org.eclipse.cosmos.common
org.eclipse.cosmos.dc.broker.client
org.eclipse.cosmos.dc.dataManager
org.eclipse.cosmos.dc.dataManager.client
org.eclipse.cosmos.dc.dataManager.common
org.eclipse.cosmos.dc.example.mdr.source
org.eclipse.cosmos.dc.framework.source
org.eclipse.cosmos.dc.logging.datamgr
org.eclipse.cosmos.dc.logging.datamgr.client
org.eclipse.cosmos.dc.logging.datamgr.common
org.eclipse.cosmos.dc.logging.datamgr.source
org.eclipse.cosmos.dc.management.domain.client
org.eclipse.cosmos.dc.mdr
org.eclipse.cosmos.dc.mdr.client
org.eclipse.cosmos.dc.mdr.common
org.eclipse.cosmos.dc.mdr.registration
org.eclipse.cosmos.dc.mdr.registration.client
org.eclipse.cosmos.dc.mdr.registration.common
org.eclipse.cosmos.dc.source
org.eclipse.cosmos.dc.stat.datamgr
org.eclipse.cosmos.dc.stat.datamgr.client
org.eclipse.cosmos.dc.stat.datamgr.common
org.eclipse.cosmos.dc.stat.datamgr.source
org.eclipse.cosmos.example.mdr
org.eclipse.cosmos.example.mdr.registration
org.eclipse.cosmos.example.mdr.web
org.eclipse.cosmos.me.dmtoolkit.source
org.eclipse.cosmos.me.management.common
org.eclipse.cosmos.me.management.source
org.eclipse.cosmos.me.management.wsdm
org.eclipse.cosmos.rm.sml.mdr
org.eclipse.cosmos.rm.source
org.eclipse.cosmos.samples.cmdbf.services
Comment 7 David Whiteman CLA 2008-03-28 13:10:02 EDT
Some (but not all) of these have already been fixed now.
Comment 8 Saurabh Dravid CLA 2008-03-31 12:14:40 EDT
Following plugins needs to have qualifier in version string.

org.eclipse.cosmos.dc.example.mdr.source
org.eclipse.cosmos.dc.framework.source
org.eclipse.cosmos.dc.logging.datamgr
org.eclipse.cosmos.dc.logging.datamgr.client
org.eclipse.cosmos.dc.logging.datamgr.common
org.eclipse.cosmos.dc.logging.datamgr.source
org.eclipse.cosmos.dc.management.domain.client
org.eclipse.cosmos.dc.source
org.eclipse.cosmos.dc.stat.datamgr
org.eclipse.cosmos.dc.stat.datamgr.client
org.eclipse.cosmos.dc.stat.datamgr.common
org.eclipse.cosmos.dc.stat.datamgr.source
org.eclipse.cosmos.example.mdr
org.eclipse.cosmos.example.mdr.registration
org.eclipse.cosmos.example.mdr.web
org.eclipse.cosmos.me.dmtoolkit.source
org.eclipse.cosmos.me.management.common
org.eclipse.cosmos.me.management.source
org.eclipse.cosmos.me.management.wsdm
org.eclipse.cosmos.rm.sml.mdr
org.eclipse.cosmos.rm.source
org.eclipse.cosmos.samples.cmdbf.services
Comment 9 Leonard Richardson CLA 2008-04-15 09:13:15 EDT
Created attachment 96063 [details]
Patch to ignore .source plugins

This patch makes the plugin qualifier check ignore plugins with .source in their name.
Comment 10 Saurabh Dravid CLA 2008-04-23 15:02:07 EDT
Please change the status of this bug. We have script to check the qualifier string in plugin version.
Comment 11 Leonard Richardson CLA 2008-04-24 03:37:52 EDT
This is now resolved
Comment 12 David Whiteman CLA 2008-10-15 09:58:27 EDT
Saurabh, if this fix was made prior to Leonard earning committer status, it should be marked as IPLog, else it shouldn't.
Comment 13 David Whiteman CLA 2008-10-15 11:55:31 EDT
I think you and I are not applying the iplog flag correctly.  I think we need to go into the Details for each attachment and mark them there, rather than doing it for the entire defect.