[jbosstools-issues] [JBoss JIRA] (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:all-tabpanel ]

Rob Stryker updated JBIDE-8866:
-------------------------------

    Fix Version/s: LATER
                       (was: 4.0.x)


I am pushing this off until the next next release. As of now, our 4.0.0 will be targeting Juno SR2, and so this jira no longer really makes sense. 

However, as we move our processes to match the NEXT stream, this will become more important. So, pushing this off to the unknown. :( 
                
> 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: Rob Stryker
>             Fix For: LATER
>
>         Attachments: hibernate-tools.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira