Hi,Agree it make sense ;)Thanks!regards,FrancoisEnvoyé depuis mon smartphone
Samsung Galaxy.
Message d'origine De : Andrea Cosentino
Date : 15/03/2019 12:00 (GMT+04:00) À : dev
Objet : Re: [DISCUSS] Flat POMs I think it may be a good
improvement.--Andrea Cose
Hi Cameleers,
I've created CAMEL-13331[1], I'll start working on a PR and we can
take it from there, would be good to get it done before we release the
next milestone of Camel 3 and gather some feedback. With such a wide
ecosystem and use cases it's a bit hard to make these changes without
breaking
Hi
Yeah sure if something can improve the build and maintenance of our
huge Camel project then that would be great.
On Thu, Mar 14, 2019 at 5:15 PM Zoran Regvart wrote:
>
> Hi,
> when we deploy POMs to Maven repository they contain a lot of
> information that relates solely to the build: the who
I think it may be a good improvement.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, March 15, 2019, 2:05:53 AM GMT+1, Willem Jiang
w
+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 separatel
Hi,
when we deploy POMs to Maven repository they contain a lot of
information that relates solely to the build: the whole ``
section, `` 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 t
