How to implement an organisational super pom ?

[Dhananjay Nene]

I need to implement a common pom which can be inherited by a large 
number of projects. However the common pom does not reflect a top level 
module and does not have any sources or artifacts (since it is used only 
for inheritance). My attempts so far lead me to believe that maven 
requires me to assign a version to the common pom, and the release 
management workflow tries to checkout a project corresponding to top 
level pom which obviously fails in my case. How can I implement a common 
pom (like the maven super pom) so that the common pom is used only for 
inheritance, and each pom which refers to it (as a parent ??) is in fact 
a top level application (and not a module/sub module) ?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]