Thanks Andrey for this reminder!
> If after that you see API errors in the workspace,
One important addition here: some plug-ins and even the default workspace
have some problems being reported as warning. So, you also need to check
whether there are new API related warnings. Even better,
Everyone can do this ;-).
Dani
From: Lars Vogel
To: "Eclipse platform general developers list."
Date: 09.05.2019 10:49
Subject:Re: [platform-dev] API changes in SDK
Sent by:platform-dev-boun...@eclipse.org
> One important addition here: some plug-ins and even the
> Would be nice to see you contributing to this effort Dani and you
already seem to know the affected projects.
No I don't. One has to look at each project.
Maybe anyone who notices it in one of its projects just fixes it.
Dani
From: Lars Vogel
To: "Eclipse platform general
OK, I looked at this.
Almost all projects are taking those options from the workspace settings
(even if project specific settings are specified, see
https://bugs.eclipse.org/546861). Therefore, we could get the biggest
improvement by changing the minor/major version preferences from 'Warning'
Thanks, Dani. I will help with
https://bugs.eclipse.org/bugs/show_bug.cgi?id=547138
On Thu, May 9, 2019 at 3:02 PM Daniel Megert wrote:
>
> OK, I looked at this.
>
> Almost all projects are taking those options from the workspace settings
> (even if project specific settings are specified, see
Hi,
I don't know if this is the right place to ask this. I am developing a
gamedev IDE and I need a custom Project Explorer more friendly with game
development. I use a custom Tree widget that has all the features I
need: zoomable, quick filtering, flexible layout, etc.. So what I need
is to
I agree with Andrey in principle !
In short, before submitting any gerrit patch, just keep the default
workspace settings and run API tools analysis
( clean->build all) after setting the correct baseline. Ensure that none of
the settings has been made more lenient
(error changed to warning or
If only the correct baseline were automatically set... And all the
preferences too. I wonder how we could possibly do that?
It seems pointless to me to record all these important details in an
email thread. Record them in a wiki, if you feel these are important
details that are best
Hi,
Just one question: what are the exact features of your custom tree widget
that couldn't be implemented with a regular (or CNF) Tree? Quick-filtering
is possible, zoomable I guess is also feasible by dealing with text and
image size...
If you can manage to use a regular tree, then you can just
> One important addition here: some plug-ins and even the default workspace
Dani, please open a bug for that and list the project which uses this
project setting. We should adjust that.
On Thu, May 9, 2019 at 10:42 AM Daniel Megert wrote:
>
> Thanks Andrey for this reminder!
>
> > If after that
Andrey,
Perhaps folks should rather consider consistently using the same
automated setup so that everyone consistently see the same thing as
everyone else. That's the purpose of the Oomph setup: to avoid all the
manual steps you describe here.
Regards,
Ed
On 08.05.2019 21:20, Andrey
Right,
I forgot to add another points where we can help ourselves:
- contribute to the https://wiki.eclipse.org/Platform_UI wiki, describe the API
maintenance
- add a "welcome page" for new contributors on thwe wiki, describe what is
important to know (API maintenance, watching
Hi Mickael,
I'm also bad with API Tools. Unfortunately I also have the impression
that least for deleting API the API tooling is buggy and as I'm mainly
the person who deletes API it usually hits me. Unfortunately I'm not
able to reproduce this bugs recently.
Examples for possible API tools
Hi,
While I understand Andrey and others and fully agree with them on the
necessity and value of project respecting API rules and process for that
-while I am one of the "worst citizen" on that matter in practice-, I think
any proposal that involves enforcing developers to use or setup anything
Andrey,
Comments below.
On 09.05.2019 10:10, Andrey Loskutov wrote:
Ed,
While we use Oomph in the lab (thanks for the tool!), I can't use Oomph for SDK
development,
Why not? I've certainly used to to make contributions to the Platform UI.
and also Oomph leads to problems where
Would be nice to see you contributing to this effort Dani and you
already seem to know the affected projects.
Best regards, Lars
On Thu, May 9, 2019 at 11:07 AM Daniel Megert wrote:
>
> Everyone can do this ;-).
>
> Dani
>
>
>
> From:Lars Vogel
> To:"Eclipse platform general
16 matches
Mail list logo
