Copy stable releases to https://download.jboss.org/jbosstools/vscode/stable/vscode-java

[fbricon]

Upon publishing to the Marketplace, releases are copied to https://download.jboss.org/jbosstools/static/jdt.ls/stable/

As @apupier pointed out, to make it more consistent with the other vscode extensions at Red Hat, we should move the binaries to https://download.jboss.org/jbosstools/vscode/stable/vscode-java instead.

That means:

• updating the Jenkinsfile
• move existing releases from https://download.jboss.org/jbosstools/static/jdt.ls/stable/ to https://download.jboss.org/jbosstools/vscode/stable/vscode-java (poke @nickboldt)

[fbricon]

vscode-java/Jenkinsfile

Lines 75 to 76 in e0490ac

	stage "Publish to http://download.jboss.org/jbosstools/static/jdt.ls/stable/"
	// copy this stable build to Akamai-mirrored /static/ URL, so staging can be cleaned out more easily

@nickboldt : does it mean https://download.jboss.org/jbosstools/vscode/stable/ is not Akamai-mirrored ?

[nickboldt]

if your bits re not under the /static/ then you're not getting Akamai edge mirroring.

on the flip side, if you are building lots of CI / nightly builds, please don't put them in /static/ since they'll slow down mirror performance.

[fbricon]

mmm that means all other vscode stable releases should be moved to /static/ then

[fbricon]

Stable releases are copied to https://github.com/redhat-developer/vscode-java/releases.
We're no longer using Jenkins so can't write to https://download.jboss.org/jbosstools/static/jdt.ls/stable/" anymore.

Closing as won't fix.