To be honest, I don’t consider duplicate mapping IDs as a problem users often run into. I almost think that this never happened to me before. I try to follow a naming schema that prevents conflicts. Something like “customerList”, “customerCreate”, “customerModify”, ….
The only thing I could imagine that could perform such compile time checks would be a maven plugin or something like this. But I think this would be hard to implement, because you would have to duplicate much of the bootstrapping code of PrettyFaces to get the effective mapping ids (parsing pretty-config.xml and scanning for annotations).
I for myself don’t see much of a benefit for such compile time checks. Especially there isn’t much beside duplicate mapping IDs that you can look for at compile time. But if you think this could be useful for you, we are always happy to get contributions. 🙂
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.