Re: [platform-dev] API changes in SDK

[Ed Merks <ed.merks@xxxxxxxxx>]

Nikita,

Of course you haven't bothered to report a problem.  And even if you did, in the end, I have to question why should I bother to fix setup problems for the platform in the first place when practically no one uses the results anyway.  I will just make sure the things I personally use, e.g., the setup for Platform UI, work for me.  Everyone else can joyfully have their own opinionated opinions and we can continue to have a glitchy development processes in need of copious documentation spread around in hard-to-find places.  None of that affects me personally and it's clearly futile to try to improve anything for anyone else.

So yes, it's highly unfortunate that the platform development setup is so complicated.   But even if it were simple, that still wouldn't be a good argument to do in manually.  The only good argument would be that there is no automatic approach that works.

Regards,
Ed

On 11.05.2019 11:48, Nikita Nemkin wrote:

On Fri, May 10, 2019 at 2:26 PM Ed Merks <ed.merks@xxxxxxxxx> wrote:

With the Oomph setup, the baseline is always set up automatically.    There are Oomph setups for the entire darned Eclipse SDK along with detailed documentation:

  https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning

I've had nothing but trouble with Oomph setup in the past. It's glitchy and opinionated.

In fact, the procedure described in the wiki fails for me even now (some generic text editor bundle is missing during installation).

It's unfortunate that platform development setup is so complicated that it has to be automated.

Best regards,

Nikita Nemkin

_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev