[jbosstools-issues] [JBoss JIRA] (JBIDE-18773) Ensure features and plugins have upversioned since 4.2.0.Final release [JavaEE]

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-18773:
----------------------------------------

missing version updates are blocking issues thus setting priority accordingly.

Also this is most efficiently done by running the following command in the root of the projects/component that need to bump versions.

{code}
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.3-SNAPSHOT
{code}

(of course remember to update 1.2.3-SNAPSHOT to the right version)

Details in this blog: https://developer.jboss.org/en/tools/blog/2011/09/17/coping-with-versions-in-large-multi-module-osgi-projects

> Ensure features and plugins have upversioned since 4.2.0.Final release [JavaEE]
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-18773
>                 URL: https://issues.jboss.org/browse/JBIDE-18773
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: cdi, cdi-extensions
>    Affects Versions: 4.2.1.CR1
>            Reporter: Nick Boldt
>            Assignee: Alexey Kazakov
>             Fix For: 4.2.1.CR1
>
>
> You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins are still at 1.6.0:
> https://github.com/jbosstools/jbosstools-javaee/blob/c7a07c9a31955213c2bcdfedd022abdbfafa677f/cdi/plugins/org.jboss.tools.cdi.core/META-INF/MANIFEST.MF#L5
> Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)