* resolving the anootation processor paths in multiple requests can easily
   lead to duplicated dependencies, e.g. if two processors depend on
   the same transitive dependency. Ultimately, both versions would end-up on
   processorpath, but of course only one of them would be used
   (likely dependeing on the order of elements of processorpath)

 * the previous behavior also did match the general rules of dependency
   resolution used by Maven itself and other plugins

 * this may potentially be a breaking change for certain corner cases,
   if for example some projects mistakenly rely on the order of elemenets in
   processorpath