Re: [unide-dev] non-java artifacts on repo

[Frank Patz-Brockmann <frank.patz-brockmann@xxxxxxxxxxxxxxxxxxxx>]

Am 23.01.2018 um 11:01 schrieb Meinhardt Axel (BCI/ECM2) <Axel.Meinhardt@xxxxxxxxxxxx>:

I would like to publish website & js/html5, non-java, artifact to be available for use/download.

I see several ways:

1.     Use Jenkins to deploy (a zip etc.) directly to unide.eclipse.org vm for download. For most recent version to use. We (project team) would have to organize the hosting, especially of multiple versions.

2.     Deploy to website [1]. For most recent version to use only.

3.     Use mvn deploy-file to deploy (a zip etc.) to repo.eclipse.org nexus [2]. Should the path be 
https://repo.eclipse.org/content/repositories/unide/org/eclipse/iot/unide/ppmp/ppmp-client/0.2.0-SNAPSHOT/ ?
Hosting, also of multiple versions, provided. No “online use” via browser.

4.     Configure an eclipse npm on nexus [3][4]. Versioning provided, no ‘use’ via browser.

5.     Just use github with gh-pages [5]. Versioning provided, but just for complete repository (not individual subdirectories)

 

I think we should deploy the most recent version to the existing website (2.[1]) and a zipped archive file to the nexus (3.) without npm support.

What do you think?

The published website should be "latest", no old versions for download. We'll have the history in GH, don't we? For the spec part, we should have different pages for different versions of the spec, if we decide to keep older versions available (which we should). Technically, gh-pages sounds easiest to me, and it would support Markdown, which makes writing a lot more convenient. OTOH, we would have the pages under https://eclipse.github.io/unide (being project pages), which is not great. We could have GH pages serving unide.eclipse.org, but that would require work by Eclipse's DNS masters. Is that possible?

Just my 5 cents,

- frank