Eclipse updating indexes forever

As a result, it is possible that the favoured selection will not be the ultimate choice.

The final decision will be made by the EMO Executive Director (“EMO(ED)”) in consultation with the PMC. Names can be nominated by anyone in the community via this Git Hub Issue record.

If it doesn’t, then we would have been better off without it.

At Java One this year, I described a battle we once had between two prepositions for naming our collection factory methods in the Eclipse Collections API.

During the summer of 2014, my team was responsible for implementing the redesign of Bug 432342 - Website Redesign 2014.

We are planning on removing the Nova theme from eclipse.org-common on December 5th, 2017.

The battle was between After an intense debate, we wound up with both options for our collection factory classes. This makes them unsuitable for writing code fluently.

We thought this was one place where we could provide multiple options to allow developers to use their own preference. Sometimes there is more than just a single battle to be won. We have our own Mutable interfaces in Eclipse Collections, so we knew we could fix the fluency problem by using a one of the two prepositions.

The best way to do that, is to run your names by other developers you work with you to get a consensus before settling on a name.

On very rare occasions where a consensus is not possible (e.g.

Leave a Reply