[jbosstools-issues] [JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

Nick Boldt (JIRA) issues at jboss.org
Thu Mar 19 19:27:19 EDT 2015


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

Nick Boldt commented on JBIDE-19346:
------------------------------------

Circular release process dependency: 
* publish something to download.jboss.org as latest stable milestone
* pull that file into the staging site, update it as required 
* push that staging site to download.jboss.org, replacing the previous stable milestone w/ the new one
* pull that file into the staging site, update it as required 
* push that staging site to download.jboss.org, replacing the previous stable milestone w/ the new one
* ... 

But for the first Alpha of a cycle, we need to create the file on download.jboss.org BEFORE there's a published milestone, in order to publish the milestone. So, as you can see, we need to bootstrap the pull-then-push process with a dummy file. 

This is no crazier than when we create empty update sites in /development/ or /stable/ until there's content to put there. It's just another bootstrapping step we have to do to prepare for the new year's release. 

My point was simply that we need to DOCUMENT this in the release guide.

> jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-19346
>                 URL: https://issues.jboss.org/browse/JBIDE-19346
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 4.3.0.Alpha2
>
>
> While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ?
> {code}
> $➔ cat jbosstools-earlyaccess.properties
> #Mon Sep 01 18:54:14 CEST 2014
> org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63]
> org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649]
> org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218]
> {code}
> -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jbosstools-earlyaccess.properties



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)



More information about the jbosstools-issues mailing list