[jbosstools-issues] [JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 / 9.1.0

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3562:
----------------------------------

Using the two commands Denis mentioned in the email thread about this might be simpler than rebuilding everything:

{code}mvn clean install -Djbosstools-site=https://devstudio.redhat.com/9.0/stable/updates/ -Dno-target-platform -DBUILD_ALIAS=GA -f p2-director/pom.xml && mvn clean install -Djbosstools-site=https://devstudio.redhat.com/9.0/stable/updates/ -Dno-target-platform -DBUILD_ALIAS=GA -f installer/pom.xml -P hudson,eap,pack200 -Dtpc.version=4.51.0.Final -DBUILD_NUMBER=8 -DJOB_NAME=devstudio.product_9.0.1.mars -Dupdate.site.description="Stable Release" -Djbosstools_site_stream=4.3.mars{code}

We can even revert most of the upversioning to 9.0.1 if we're OK with the idea that the installer will say 9.0.1.GA but then JBDS itself (Splash screen, About screen, features, plugins) will all say 9.0.0.GA:

https://github.com/jbdevstudio/jbdevstudio-product/pull/350 (all files put back to 9.0.0 except installer/pom.xml)

Is this something we want?

Are we OK with the installer being versioned *9.0.1.GA* but its *CONTENTS* being 9.0.0.GA ?



> Prepare for 9.0.1 / 9.1.0 
> --------------------------
>
>                 Key: JBDS-3562
>                 URL: https://issues.jboss.org/browse/JBDS-3562
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 9.0.1.GA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 9.0.1.GA
>
>         Attachments: 900GAvs901GA_B6.p2diff.txt
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.1.x
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.



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