Yeah this makes complete sense and I think I will start to following this process as well. Cheers for the examples
Trent On 27/09/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote:
See the top of http://svn.sourceforge.net/viewvc/spring-rich-c/trunk/spring-richclient/core/pom.xml?view=markup It inherits from http://svn.sourceforge.net/viewvc/spring-rich-c/trunk/spring-richclient/pom.xml?view=markup Trent Rosenbaum wrote, On 2006-09-26 5:30 PM: > So you have a pom.xml file that represents your company/organisation. > Within this file you define the plugin versions. > Then do you make this the parent to all of your projects? > > > Trent > > On 26/09/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: >> >> I always lock down the plugin versions in my parent project's >> pluginManagement. >> That way all childprojects inherit those version and it is shared to the >> other people of my team. If you do in it your home dir, it's not >> shared with your team (but it is shared for all your projects). >> >> alexsun wrote, On 2006-09-26 12:19 PM: >> > Is it posible to set up java version for all maven plugins, that >> used in >> > project, in one place? >> > And forget about it? )) >> >> -- >> With kind regards, >> Geoffrey De Smet >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- With kind regards, Geoffrey De Smet --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
