[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8866) Move all plugins up to baseline

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600242#comment-12600242 ] 

Rob Stryker commented on JBIDE-8866:
------------------------------------

I would like to stress that component owners should *REVIEW AND TEST* these paches, as they have been generated via scripts and utility programs! Do not blindly commit a patch without verifying it functions properly. While most will work, it is very possible some are completely incorrect (such as the xulrunner ones) and do not apply. 

> Move all plugins up to baseline
> -------------------------------
>
>                 Key: JBIDE-8866
>                 URL: https://issues.jboss.org/browse/JBIDE-8866
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng
>    Affects Versions: 3.3.0.M2
>            Reporter: Rob Stryker
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.M2
>
>         Attachments: manifests.zip
>
>
> Not really sure who to assign this to, short of making three dozen separate jira issues ;) I have 33 patches, one for each module, which modify all manifest.mf version numbers (in plugins, not in tests) to be brought up to our current baseline. 
> So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a dependency on this.specific.runtime  into  this.specific.runtime;bundle-version="3.6.200".  If a plugin currently reads this.specific.plugin;bundle-version="3.5.0", it will move it up to this.specific.runtime;bundle-version="3.6.200". 
> Etc. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira