In stacks.yaml, the purpose of url vs downloadUrl seem inconsistant. I believe this should be cleared up and defined more clearly in a comment.

As I understand it, downloadUrl should be a url which, once accessed, immediately begins a download of the targeted runtime. The values for JPP-6 and EAP-6.1 beta do not do this, and both require custom configuration.

From EAP 6.1 beta:

url: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=appplatform&version=6.1.0+Beta
downloadUrl: https://www.jboss.org/download-manager/content/origin/files/sha256/64/644eedc15c62d9264dbbc442f69189e9915dfdba447eaa990ed10bea299d03a3/jboss-eap-6.1.0.Beta.zip

From JPP-6:

url: http://www.jboss.org/jbossas
downloadUrl: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=jbportal&version=6.0.0

I would imagine that URL should link to a description of the targeted technology, runtime, etc, and, as mentioned above, downloadUrl should immediately or through redirects lead to a download. This doesn't seem to be happening for these two values.

For EAP6.1 beta, it does allow me to download it directly after logging in to JIRA or other community environment, however this is not suitable for non-browser based download methods. When trying to access jpp-6, it requires me to log in to the customer portal (and then for me returns that I don't have access. Ha!).

Perhaps we should require a label that indicates further user-interaction is needed than non-browser based downloads.