[jbosstools-dev] JBTIS update site on JBoss Tools web site

Max Rydahl Andersen max.andersen at redhat.com
Wed May 8 13:43:11 EDT 2013 

there is no change - this is an addition/actual release.

/max

----- Original Message -----
> When will this change take place? Do we have a target date or milestone?
> 
> 
> Thx!,
> Len
> 
> 
> (Sent from my iPhone)
> 
> 
> 
> On May 8, 2013, at 10:11 AM, Nick Boldt <nboldt at redhat.com> wrote:
> 
> > +1 to removing the word "aggregate" from the final path.
> > 
> > Existing convention is /release-type/eclipse-version/project-name/:
> > 
> > http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/
> > 
> > Thus in future if we follow that we'd want:
> > 
> > http://download.jboss.org/jbosstools/updates/development/juno/integration-stack/
> > http://download.jboss.org/jbosstools/updates/stable/juno/integration-stack/
> > 
> > and
> > 
> > http://download.jboss.org/jbosstools/updates/development/kepler/integration-stack/
> > http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/
> > 
> > 
> > On 05/07/2013 06:21 PM, Max Rydahl Andersen wrote:
> >> On Tue, May 07, 2013 at 03:10:06PM -0400, Nick Boldt wrote:
> >>> Internal component URLs? Nope, they're composite site pointers to the
> >>> latest aggregate sites.
> >> 
> >> yes - so they are internal urls - not stable/public ones (since just
> >> pointing to latest published)
> >> 
> >>> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/
> >>> 
> >>> 
> >>> http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/
> >>> 
> >>> 
> >>> 
> >>> And an aggregate can only contain ONE site, unless you mean via
> >>> <references> in its metadata, to additional upstream sites used to
> >>> resolve missing dependencies (eg., the update site can point at its
> >>> target platform site so that things like UML2 and Zest can be found).
> >> 
> >> If it only can contain one site why is it called "aggregate" and why
> >> should the name contain that ?
> >> 
> >>> Are you suggesting that
> >>> http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/4.0.0
> >>> 
> >>> should not be the latest snapshot for 4.0.0, but rather a composite site
> >>> pointing at the ACTUAL 4.0.0 site? Because if so, that's what
> >>> http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/
> >>> 
> >>> is for. Obfuscating it a level further seems redundant.
> >> 
> >> no, im saying "aggregate" has no meaning here and a
> >> simpler/shorter/following our convention for
> >> the jbosstools core site would be more fitting.
> >> 
> >> like:
> >> http://download.jboss.org/jbosstools/updates/{development|stable}/{juno|kepler}/integration-stack
> >> ?
> >> 
> >> Paul suggested
> >> http://download.jboss.org/jbosstools/updates/stable/integration-stack/kepler/
> >> 
> >> which is doable too. Quesiton is just if we want kepler/* to contain the
> >> sites, or if makes more
> >> sense to have the "distro" first. I don't have a big preference here - I
> >> just prefer that we are consistent.
> >> This url is also what should be used in central since it is what will be
> >> pointed to by users p2 metadata.
> >> 
> >> WDYT? (these sites can just be pointers to the internal component urls
> >> like the "aggregate" sites above assuming they dont change - but wether
> >> the site is an aggregate or not seems rather irrelevant and noisy to put
> >> in the main
> >> urls)
> >> 
> >> Any issues/concerns on this ?
> >> 
> >> /max
> >> 
> >>> 
> >>> On 05/07/2013 12:41 PM, Max Rydahl Andersen wrote:
> >>>> On Tue, May 07, 2013 at 09:15:02AM -0400, Nick Boldt wrote:
> >>>>> Uh, guys... you're reporting & solving a problem that doesn't exist.
> >>>> 
> >>>> uh nick - the links below are all "internal component" urls...aggregate
> >>>> can contain multiple sites.
> >>>> 
> >>>> Any reason why not to put JBTIS release into the url Paul suggested -
> >>>> this url could of course refer to these
> >>>> "internal" sites (Whichever is appropriate - specific version or the
> >>>> composite/aggregate) ?
> >>>> 
> >>>> /max
> >>>> 
> >>>>> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/
> >>>>> 
> >>>>> 
> >>>>> is already a "stable" URL insofar as it contains no version number - it
> >>>>> is a composite site pointing at the latest version, which is currently
> >>>>> 4.1.0 but will be 4.1.1 when/if that happens. Problem already solved.
> >>>>> 
> >>>>> Similarly,
> >>>>> http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/
> >>>>> 
> >>>>> 
> >>>>> contains no version number - it too is a composite site.
> >>>>> 
> >>>>> Thus all you need to do, when you're ready to promote an "integration"
> >>>>> site to a more stable release type, is to copy its contents to a
> >>>>> similarly-patterned URL, such as:
> >>>>> 
> >>>>> http://download.jboss.org/jbosstools/updates/*development*/juno/integration-stack/aggregate/
> >>>>> 
> >>>>> 
> >>>>>  or
> >>>>> http://download.jboss.org/jbosstools/updates/*stable*/juno/integration-stack/aggregate/
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> And voila, you're released!
> >>>>> 
> >>>>> THEN... you link to the *development* or *stable* URL from
> >>>>> http://jboss.org/tools, and the world comes to visit.
> >>>>> 
> >>>>> N
> >>>>> 
> >>>>> On 05/07/2013 08:49 AM, Paul Leacu wrote:
> >>>>>> 
> >>>>>>    Hey Max -
> >>>>>>        You're correct - I just got write permissions to 'staging'
> >>>>>> this week.  I'm thinking of:
> >>>>>> 
> >>>>>> 
> >>>>>> http://download.jboss.org/jbosstools/updates/stable/integration-stack/kepler/...
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>>    for the stable location.  Then we'll deploy the .Final to the
> >>>>>> nexus staging area and then to release.
> >>>>>>    As for the juno update site - since we're now targeting SOA-P 6.0
> >>>>>> beta (kepler) the existing
> >>>>>>    url will very likely be the only one.  For kepler we'll have both
> >>>>>> the aggregated target platform (.target)
> >>>>>>    file and JBTIS 4.1.0 captured.
> >>>>>> 
> >>>>>>   --paull
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>> ----- Original Message -----
> >>>>>>> From: "Max Rydahl Andersen" <manderse at redhat.com>
> >>>>>>> To: "Andrej Podhradsky" <apodhrad at redhat.com>
> >>>>>>> Cc: "jbosstools-dev jbosstools-dev"
> >>>>>>> <jbosstools-dev at lists.jboss.org>, "Paul Leacu" <pleacu at redhat.com>
> >>>>>>> Sent: Tuesday, May 7, 2013 8:16:18 AM
> >>>>>>> Subject: Re: [jbosstools-dev] JBTIS update site on JBoss Tools web
> >>>>>>> site
> >>>>>>> 
> >>>>>>>> at JBoss Tools web page [1] you can see an obsolete update site for
> >>>>>>>> SOA/JBTIS tooling [2].
> >>>>>>>> I suggest to change it to the current JBTIS update site [3] which
> >>>>>>>> contains
> >>>>>>>> updated tools.
> >>>>>>>> 
> >>>>>>>> [1] http://www.jboss.org/tools/download
> >>>>>>>> [2]
> >>>>>>>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk
> >>>>>>>> 
> >>>>>>>> [3]
> >>>>>>>> http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/aggregate/4.0.0
> >>>>>>> 
> >>>>>>> [3] is a version specific site - we need to get a stable url to use
> >>>>>>> before
> >>>>>>> publishing to users.
> >>>>>>> 
> >>>>>>> i.e. when 4.0.1 comes out 4.0.0 won't contain the right version.
> >>>>>>> 
> >>>>>>> Paul - any progress on getting a stable url ?
> >>>>>>> 
> >>>>>>> /max
> >>>>>>> 
> >>>>>>> 
> >>>>>>>> Have a nice day!
> >>>>>>>> 
> >>>>>>>> --
> >>>>>>>> Andrej Podhradsky
> >>>>>>>> Quality Assurance Associate
> >>>>>>>> JBoss SOA Platform
> >>>>>>>> IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> _______________________________________________
> >>>>>>>> jbosstools-dev mailing list
> >>>>>>>> jbosstools-dev at lists.jboss.org
> >>>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>>>>> _______________________________________________
> >>>>>> jbosstools-dev mailing list
> >>>>>> jbosstools-dev at lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>>>> 
> >>>>> --
> >>>>> Nick Boldt :: JBoss by Red Hat
> >>>>> Productization Lead :: JBoss Tools & Dev Studio
> >>>>> http://nick.divbyzero.com
> >>>>> _______________________________________________
> >>>>> jbosstools-dev mailing list
> >>>>> jbosstools-dev at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> >>> 
> >>> --
> >>> Nick Boldt :: JBoss by Red Hat
> >>> Productization Lead :: JBoss Tools & Dev Studio
> >>> http://nick.divbyzero.com
> >>> _______________________________________________
> >>> jbosstools-dev mailing list
> >>> jbosstools-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> > 
> > --
> > Nick Boldt :: JBoss by Red Hat
> > Productization Lead :: JBoss Tools & Dev Studio
> > http://nick.divbyzero.com
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 

-- 
/max

More information about the jbosstools-dev mailing list