[jbosstools-issues] [JBoss JIRA] (JBIDE-20779) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-20779:
------------------------------------

build (parent pom): done
build-sites: done
dl.jb.org: nothing to do
devdoc: nothing to do (at least until we start WRITING new doc that's only for 4.4.x)

build-ci: not done yet -- need to branch from 4.3.x to 4.4.x (master is still deprecated) & update/clone job(s)
versionwatch: not done yet

maven-plugins: leaving that for [~mickael_istria] to do


> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-20779
>                 URL: https://issues.jboss.org/browse/JBIDE-20779
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; 
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.4.0.Alpha1-SNAPSHOT</version>
>   </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.0.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.0.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22build%22%29]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)