Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Include Git in the SDK
Hi Rolf/Tom,

Yes, I know Oomph. It is fantastic, and we use it in the BIRT and WB projects. It is a great success attracting new BIRT developers because they (new contributors) are ready to program in 15 minutes. -> (https://github.com/eclipse/birt)  We should definitely have this for platform once the move to Github is complete.

Thanks for mentioning Oomph again.

Regarding my request:
Tom uses the install-once-and-update workflow, you use the oomph workflow, but I throw away the old SDK and unzip a fresh one.

No big problem, I just thought, since EGit is such an essential tool, it would be nice to include it.

Cheers,

Wim



On Thu, Dec 2, 2021 at 8:29 AM Rolf Theunissen <rolf.theunissen@xxxxxxxxx> wrote:
Hi Wim,

I think that there is already a *great* solution for provisioning Eclipse Environments, including the Eclipse Platform SDK: Oomph. It seems that the power of the tool is still not well understood. Using the instructions on the wiki [1], it is literally a few clicks to set up an Eclipse SDK including *all* (not only EGit/JGit) dependencies to build and develop the tools. For instance, EMF Tools and E4 Tools are installed when doing platform UI development. Note that these tools will not be installed if you don't include the Platform UI project, so even a minimal set of dependent tools is installed.

Moreover, it is straightforward to define custom configurations for Products and Platforms. You could create and publish a SDK Product configuration that includes EGit next to the existing SDK. Also, for the more advanced user, you could even use user-configuration to install some features in every Eclipse instance you install with Oomph.

IMHO, the Oomph configurations take care of 'the thooling we rely on', without polluting the SDK product or development environments of others.

Best Regards,
Rolf


Op wo 1 dec. 2021 om 13:00 schreef Wim Jongman <wim.jongman@xxxxxxxxx>:
Hi,

I know that the aim of the SDK is to deliver what we make here at Platform, but it is very inconvenient that Git is not included in the SDK.

How do you feel about broadening the definition of the SDK:

The SDK includes everything that Platform builds plus the tooling we rely on.

Cheers,

Wim
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev

Back to the top