As discussed in the milestone discussions, I also get at startup those warnings:
[WARN ] [ore.common.registry.AbstractRegistry] - Cannot add “GroupItem” with key “gGlobal”. It exists already from provider “GenericItemProvider”! Failed to add a second with the same UID from provider “ManagedItemProvider”!
All my items are defined in *.items files. The warning arises when the file with the definition of the GroupItem is loaded.
As far as I can see, the mentioned GroupItem is used in the definition of other items, defined in files loaded before. Obviously the GroupItem is also created when used, not only when defined.
The order of loading the .items files looks quite random. Is there a possibility to force a certain file to be loaded first?