I think it may be a good improvement. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: [email protected] Twitter: @oscerd2 Github: oscerd
On Friday, March 15, 2019, 2:05:53 AM GMT+1, Willem Jiang <[email protected]> wrote: +1. >From my experience, use the profile to support Spring 4.x and Spring 5.x at the same time. In the maven deploy time, we have to choose one of the profile to use. The flatten maven plugin could address this kind of problem, we could deploy Spring 4.x version pom and Spring 5.x version separately. In this way, the user can choose what kind of version they want to use. Anything thoughts? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 15, 2019 at 12:15 AM Zoran Regvart <[email protected]> wrote: > > Hi, > when we deploy POMs to Maven repository they contain a lot of > information that relates solely to the build: the whole `<build>` > section, `<profiles>` and such. > > I'm looking at flatten-maven-plugin[1] and I think with 3.0 we have an > opportunity to cleanup our published POMs. > > I can raise a JIRA for this, but I think it's worth discussing and see > if anyone has any big objections to doing that? > > zoran > > [1] www.mojohaus.org/flatten-maven-plugin/ > -- > Zoran Regvart
