Currently there are two methods - isAfter, isBefore methods both returning Set<String>. These are used for plugin ordering.

But, there are problems:

1) plugins are ordered based on category and then ordered by isAfter/isBefore within the category!

2) Plugins must know each-other by name to use this isAfter/isBefore method overrides [in addition to being plugins of same category].

We need some other solution for ordering (if at all!). For now, it is better to remove isAfter/isBefore to avoid API pollution.

None of the internal plugins use that. There is only a specific test class that uses these to exercise the API!