Hi,Agree it make sense ;)Thanks!regards,FrancoisEnvoyé depuis mon smartphone
Samsung Galaxy.
-------- Message d'origine --------De : Andrea Cosentino
<[email protected]> Date : 15/03/2019 12:00 (GMT+04:00) À : dev
<[email protected]> Objet : Re: [DISCUSS] Flat POMs I think it may be a good
improvement.--Andrea Cosentino ----------------------------------Apache Camel
PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail:
[email protected]: @oscerd2Github: oscerdOn 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 Spring5.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 coulddeploy Spring
4.x version pom and Spring 5.x version separately. Inthis way, the user can
choose what kind of version they want to use.Anything thoughts?Willem
JiangTwitter: willemjiangWeibo: 姜宁willemOn 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
