Well ... documentation is good, but enforcement and a friendly but clearly phrased error message containing:
1. What is wrong with the current naming, 2. What should be done to correct the problems, and 3. A reference to further reading on the topic (for example *why* something is enforced) ... is even better, in that it works. That is the only functional way in a large organisation, and I believe the maven community can be perceived as such. 2013/6/18 Christian Schulte <c...@schulte.it> > Am 06/18/13 17:32, schrieb Stephen Connolly: > > relocation pom will not work for plugins... (we maybe should look into > that > > though) > > > > Simplest is just to move to the new ID and tell your users to change... > > that's what jetty did > > Ok. Thanks for clarifying. > > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- +==============================+ | Bästa hälsningar, | [sw. "Best regards"] | | Lennart Jörelid | EAI Architect & Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype): jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==============================+
