You can create a super-parent POM, which defines only the distribution repositories. This is very unlikely to change therefore having all your projects to extend this one should be relatively safe.
M. On Fri, 2010-05-07 at 05:00 +0530, Lahiru Gunathilake wrote: > Hi Ron, > > In my case I have so many modules which are having so many parent poms :( > > Lahiru > On Wed, May 5, 2010 at 5:24 PM, Ron Wheeler > <[email protected]>wrote: > > > On 05/05/2010 1:36 AM, Lahiru Gunathilake wrote: > > > >> Hi all, > >> > >> I have tons of pom files in my project and each file is having its own > >> maven > >> repository listed in their distributionmanagement elements, so I want to > >> use > >> a single repo to do the mvn deploy and point my repository using > >> settings.xml file. > >> > >> I like to know whether this is possible with maven 2.1.0 or not, if this > >> is > >> possible can someone please point me on how to do that ! > >> > >> Thanks in advance > >> Lahiru > >> > >> > >> > > Wouldn't that be easier in a parent pom? > > The project poms would not have any distribution management which makes > > them a lot simpler. > > > > Ron > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
