[jbosstools-issues] [JBoss JIRA] (JBIDE-14118) Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0?

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBIDE-14118.
------------------------------



In JBT 4.0:

{code:title=http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno/plugins/}
org.jboss.tools.forge.core_1.1.0.Final-v20130327-0622-B107.jar
org.jboss.tools.forge.runtime.ext_1.1.0.Final-v20130327-0622-B107.jar
org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar
org.jboss.tools.forge.ui_1.1.0.Final-v20130327-0622-B107.jar
{code}

Whereas in JBT 4.1:

{code:title=http://download.jboss.org/jbosstools/updates/nightly/core/4.1.kepler/plugins/}
org.jboss.tools.forge.core_1.2.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.runtime.ext_1.2.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.runtime_1.3.2.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.ui_1.2.0.CR1-v20130628-2152-B84.jar
{code}

Plus these new plugins:
{code}
org.jboss.tools.forge.ui.ext_1.0.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.ui.notifications_1.0.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.ui.wizards_1.0.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge2.runtime_2.0.0.CR1-v20130628-2152-B84.jar
org.jboss.tools.forge.core.ext_1.0.0.CR1-v20130628-2152-B84.jar
{code}

So therefore we've upversioned correctly, and org.jboss.tools.forge.runtime is currently at 1.3.2.
                
> Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0?
> -----------------------------------------------------------------
>
>                 Key: JBIDE-14118
>                 URL: https://issues.jboss.org/browse/JBIDE-14118
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: forge, updatesite
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Koen Aers
>            Priority: Minor
>             Fix For: 4.1.0.Beta1
>
>
> In JBT 4.0.1:
> org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar
> In JBT 4.1.0.Alpha2b:
> org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar
> So timestamp goes up, but service does not?
> Should this plugin be versioned 1.2.200? Or should it be 1.3.0? Also, if you're moving up this *one* plugin, [~maxandersen] will probably want you to bump the feature/plugin versions for the whole project to the same value, 1.2.200 or 1.3.0.
> The big concern here is that we don't want Eclipse to see org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar (from JBT 4.0 / Juno) as a "newer" plugin than org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar (from JBT 4.1 / Kepler) because of the way osgi view "Final" as newer than "Alpha". 
> If both work equally well in Juno *and* in Kepler, this isn't a showstopper unless one of them prevents installation of something else in JBoss Tools due to platform conflicts.
> You can bump all poms/manifests/feature.xml files in one operation like this:
> {code:title=https://gist.github.com/nickboldt/4548933/raw/ec20825dbe7a3f07a9d388015564d2ced0f79885/upversion.sh}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=x.y.z-SNAPSHOT 
> {code}
> See also: http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws/output.html#Plugin_org.jboss.tools.forge.runtime

--
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