[jbosstools-dev] Anonymous Downloads for Alpha release, JBT, and Stacks

[Rob Stryker]

On 02/06/2015 08:40 PM, David Hladky wrote:
> Hi Rob,
>
> using the /jdf links is the right way to do on your side. However I do not understand the requiresCredentials issue is. Is it a problem on your side or does the service return you something unexcpected? If so, have you checked you saved the changes?
>
> David

Stacks.yaml has various labels we can add to their list of runtimes. One 
of the labels we added was 'requiresCredentials".  Past (and current) 
versions of jbosstools interpret this flag to mean 'go through the jboss 
download-manager workflow', where we set the custom request headers. 
Otherwise, if requiresCredentials is set to false, we basically do a 
generic wget / curl request with no xml headers at all. We treat it the 
same way as we would a zip file on sourceforge or any web server.

So if we set that to false, we would do a generic request to the jdf url 
with no request headers at all, and this in turn downloads what is an 
html page.

Does that make sense?

>
> ----- Original Message -----
> From: "Rob Stryker" <rstryker at redhat.com>
> To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>, "Rafael Benevides" <benevides at redhat.com>, "David Hladky" <dhladky at redhat.com>
> Sent: Friday, 6 February, 2015 1:30:10 PM
> Subject: Anonymous Downloads for Alpha release, JBT, and Stacks
>
> Hey all:
>
> I've made a comment over on https://issues.jboss.org/browse/JBIDE-18709
> investigating the issue of anonymous downloads as it pertains to alpha
> releases, stacks, and JBT as a group.
>
> It'd be good if those addressed directly above (david, rafael) had a
> look just so that everyone's aware of the issues of adding any Alpha
> release to JBoss Stacks.
>
> The tl;dr of it is:  if we do add alpha releases to stacks, we must
> still use the jdf URL, and we must still set requiresCredentials=true,
> even though it's not accurate. Otherwise we risk breaking older releases
> of JBT.
>
> Any questions or comments are welcome and encouraged on the jira issue
> directly.
>
> Thanks in advance.
>
> - Rob Stryker