Ok, the Website is currently a git push to [1]. I’ll figure out how to pull from github and push there automatically from jekins. I heard there’s also
another download area. I asked webmaster how that works [2].
Additionally, I could eventually publish to npmjs.com (“maven central” for js), but maybe that’s not even necessary.
[1]
https://git.eclipse.org/r/www.eclipse.org/unide
[2]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=529948
Mit freundlichen Grüßen / Best regards
Axel Meinhardt
(BCI/ECM2, Technical Lead Ecosystem)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin |
GERMANY |
www.bosch-si.com
Tel. +49 30 726112486 | Mobil +49 173 5173094 | Fax +49 30 726112-100 | axel.meinhardt@xxxxxxxxxxxx
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn
From: unide-dev-bounces@xxxxxxxxxxx [mailto:unide-dev-bounces@xxxxxxxxxxx]
On Behalf Of Frank Patz-Brockmann
Sent: Dienstag, 23. Januar 2018 12:23
To: unide developer discussions <unide-dev@xxxxxxxxxxx>
Subject: Re: [unide-dev] non-java artifacts on repo
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.
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.
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.
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?
