When you hear about a company super pom, some is mixing their references. Yes, the super pom is part of Maven and you wouldn't need to change it. What you want is a parent pom. We have a company parent pom and a program parent that refers to the company parent pom. Then each project refers to the parent pom for its program. When you put in a setting just decide 'do you want it to affect all company projects, only one program or only this project', that tells you where to put it. Just install each as a pom type artifact (and deploy if you have a repository manager).
<!-- Frank Gorham-Engard → "It is a misnomer to label any practice 'a best practice'; a practice is only best in the specific context in which it performs well." -----Original Message----- From: David Weintraub [mailto:[email protected]] Sent: Wednesday, April 07, 2010 1:49 PM To: Maven Users List Subject: Setting up Distribution Management inside of the pom.xml file When you do a "mvn deploy", Maven looks for a distributionManagement section of your POM. I would like to be able to move this distributionManagement section out of each project's POM. My developers shouldn't have to worry about it. I'd like to be able to put this in my build user's settings.xml file or in the settings.xml file inside the Maven home directory of my build system. That way, when we change the location of our release repository, I don't have to change all the various project POM files. Is this even possible? What about doing this in the company wide "Super POM"? I keep hearing about instituting a company wide Super POM, but can't find where this is suppose to go. My understanding is that the Super POM is inside the Maven JAR. Am I suppose to unjar the Maven JAR, modify the Super POM and then rejar the Maven JAR file? Or, is the company'e Super POM suppose to go somewhere else? -- David Weintraub [email protected]
