Hello, Thanks for link
1) My projects are not related to each other in form of parent child relation. So can I conclude I do not need parent pom. And I can do all via bom. 2) Can bom approach be used for plugins also. Means specific all plugin versions in bom pom and in the specific projects where I am using bom import I can write exact plugin configurations. For example declare that I am using 1.2 Maven assembly plugin. And In project I use exact configuration of the Maven assembly for the project. Thanks in advance On 13 Oct 2015 7:24 pm, "Adrien Rivard" <[email protected]> wrote: > Hi, > > A combination of parents pom and BOM is generally enough : > > Have a look at : > > https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > > > > On Mon, Oct 12, 2015 at 10:48 PM, Jagat Singh <[email protected]> > wrote: > > > Hi, > > > > What are the options then ? > > > > > > On Tue, Oct 13, 2015 at 3:46 AM, Glenn Brown <[email protected]> > > wrote: > > > > > The jcabi parent appears to be a sample maven parent pom with jcabi > > > dependencies included > > > > > > On Mon, Oct 12, 2015, 12:47 AM Jagat Singh <[email protected]> > wrote: > > > > > > > Hi, > > > > > > > > We have set of projects which have few common dependencies and > > > > configurations. > > > > > > > > How to best avoid code duplications , I have seen maven parent and > > maven > > > > jcabi parent. > > > > > > > > Are there other useful plugins to handle this. > > > > > > > > Thanks > > > > > > > > > > > > > -- > Adrien Rivard >
