Hi Jeff, This is one option and it is listed in the spring documentation. In our case, eg: we want to use newer version of jaxson and "import" is not working. The working soln is, have spring-boot-starter-parent as parent pom and over ride the jaxson version ( as listed in the doc, see the URL in my original post )
With spring-boot-starter-parent as parent pom, I'm not able to use our existing company parent pom which has lot of plugin and other tools for build. Thanks for your inputs. Regards, Subbu On Sat, Sep 19, 2015 at 1:03 AM, Jeff MAURY <[email protected]> wrote: > Use import scope for boot pom > > Jeff > Le 18 sept. 2015 19:59, "Subramanian Olagappan" <[email protected]> a > écrit : > > > Sorry.. re-sending it again. > > > > Thanks, > > Subbu > > > > On Fri, Sep 18, 2015 at 11:21 PM, Subramanian Olagappan < > [email protected]> > > wrote: > > > > > Hi, > > > > > > We have a company wide parent pom for all the projects and it has all > the > > > plugin and distribution management code. I now have a new project where > > we > > > wanted to use spring-boot-starter-parent. We also wanted to update few > of > > > the versions using the property tag [ As described in 13.1.3 of > > > > > > http://docs.spring.io/spring-boot/docs/1.3.0.M5/reference/htmlsingle/#using-boot-maven-without-a-parent > > > ] > > > > > > We don't want to create one more company parent for spring boot > projects > > > with a copy of plugin, distribution management and > > > spring-boot-starter-parent. > > > > > > Is there any way I can reuse my existing company wide parent pom to > > create > > > a parent pom for spring boot projects. > > > > > > What is the best practice to follow when you have a existing company > wide > > > parent pom and want to override few spring boot dependent versions. > > > > > > If you can give some examples, it will be helpful to me. > > > > > > Thanks, > > > Subbu > > > > > >
