Using dependencyManagement in the parent to specify the version of dependencies is also an option. IMHO that's the true Maven way, but Ron's approach could be an option in some cases. I don't like that approach though as it will create an incorrect dependency tree (dependencies will be on the wrong level and there will likely be too many dependencies).
/Anders On Fri, Dec 16, 2011 at 08:15, Ron Wheeler <[email protected]> wrote: > http://blog.artifact-software.com/tech/?p=121 > > On 16/12/2011 12:17 AM, KumarR wrote: >> >> Hi >> I am new to maven. I want to maintain a separate POM file for version of >> the jar files. This will help in maintaining the versions of jar files. >> For >> eg: if we are using junit.jar, the version of the jar file should be >> maintain in the separate POM file. This will help us in changing in only >> one >> POM rather than all the POM files if any version changes is there. Please >> help me in this regard. >> >> Regard >> Kumar >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: [email protected] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > > > --------------------------------------------------------------------- > 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]
