Hi Wim/all,
This is great - and on behalf of the CDT team I am closely following
because we will probably do the same for the CDT project.
Some notes based on my experimentation with what you provided:
- I didn't understand step 2 about "process can be tested locally" at
first. The link
It took a long struggle but our webmasters did it and we now have a very
easy website process.
1. We just edit some markdown files e.g. [1]
2. The whole process can be tested locally to make sure the changes are ok
[2]
3. The build converts the website to static HTML and pushes it to the main
> Though, it could be sufficient to write a decent manual that
> describes the way of working within the Eclipse eco-system
Developers tend to not being very attracted by reading long manuals.
Also these manuals tend to degrade over time as slight variants or
adjustments are not updated. M2E is
On 29.03.2021 08:24, Christoph Läubrich wrote:
I think I recently read about that's it is possible to have a "button"
in a html page that links to an Oomph setup file and simply creates
the IDE+checkouts and so on. I think that should be the very first
thing any project that wishes to attract
> but the index of all extension points is not. It's maintained manually
:-\
> I suggest we start a
seems the most profitable option at the moment then.
Am 28.03.21 um 20:25 schrieb Mickael Istria:
On Sun, Mar 28, 2021 at 11:29 AM Christoph Läubrich
mailto:lae...@laeubi-soft.de>> wrote:
