[
https://issues.jboss.org/browse/JBIDE-20375?page=com.atlassian.jira.plugi...
]
David Hladky commented on JBIDE-20375:
--------------------------------------
The rest service has following address:
[
https://developers.redhat.com/download-manager/rest/available]. At this moment it is
possible to narrow search to a specific product by adding a subdirectory (using a product
code). For example [
https://developers.redhat.com/download-manager/rest/available/eap].
For the web pages every download is important, but I think it makes sense to filter the
downloads for the Eclipse plugin to contain only relevant files. [~rob.stryker], I think
you know more about how they are filtered in Yaml. We would need to add this information
to DM as well and extend the rest service to enable filtering by this information. I think
it is fairly easy thing.
Also at this moment the rest service returns information about the terms and conditions
model (the requirement of the user credentials is driven by it), but I think it makes
sense to add a flag for you, that will tell you, if the specific file requires
authentication or not so you do not need to calculate it from the TC model yourself.
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
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?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)