]
Rob Stryker commented on JBIDE-20375:
-------------------------------------
I agree with Max on this point. While it was an interesting idea for download-runtimes to
use the rest service, the fact is stacks.yaml includes tons more info that we actually
*do* use. So we'd still need some way to map whatever we found in your downloadmanager
rest service to what's in stacks.yaml. This leads to duplication with no real benefit
at all.... and now we'd nede to keep more models in sync.
I don't think this idea will work for JBTools.
Investigate possibility of reading Download Manager data from a REST
service instead of YAML
--------------------------------------------------------------------------------------------
Key: JBIDE-20375
URL:
https://issues.jboss.org/browse/JBIDE-20375
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build, server, updatesite, upstream, website
Reporter: David Hladky
Download Manager has a rest service, that contains information about all downloads on
developers.redhat.com web page (and also many projects on
www.jboss.org product pages). In
the next year it will start also showing content from ITs unified Download Manager so the
number of downloads it describes will become even higher.
Because our productization team (I think [~pmuir], [~cobrien_redhat]), has to fill the
information about existing downloads to many places (from what I know they must upload it
to access.cdn, they must enter information about it to Download Manager, they must mention
it in Yaml files, they must upload it to customer portal, some of those to Unified
download manager as well...). In my opinion it is quite tedious process that we have a
chance to make less complicated.
Download manager will be a source for the product web pages and as it already contains
most of the necessary information [~wesbos] is working on it an he is fairly close to this
goal.
And if we have enough information about that why not use it and replicate the information
in a different process?