So, the goal here is to be able to provide a list of version numbers that change much easier for any release?
On Sat, Aug 17, 2013 at 3:09 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Sat, Aug 17, 2013 at 12:01 AM, Christian Müller > <christian.muel...@gmail.com> wrote: >> What do you propose the "list of all the camel components and some other >> stuff" should go? >> > > They should stay where they are. Its just all the versions that gets > moved into its own file, so the file ONLY has the versions. And that > makes the diff much easier. > >> Best, >> Christian >> ----------------- >> >> Software Integration Specialist >> >> Apache Camel committer: https://camel.apache.org/team >> V.P. Apache Camel: https://www.apache.org/foundation/ >> Apache Member: https://www.apache.org/foundation/members.html >> >> https://www.linkedin.com/pub/christian-mueller/11/551/642 >> >> >> On Thu, Aug 15, 2013 at 1:26 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> >>> Hi >>> >>> Today we have the parent/pom.xml file which has both all the versions >>> of the 3rd party JARs we have as dependencies. And also a list of all >>> the camel components and some other stuff. >>> >>> I wonder if we could have all the dependency versions in a single >>> file, without all the other stuff. >>> >>> This would make it easier for ppl to see what are the version changes >>> between any two Camel versions, but just diff the 2 files? >>> >>> And also we could just have such a link in the release notes so we >>> dont have to manually keep all the versions upgrades in the release >>> notes up to date as well. >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> Red Hat, Inc. >>> Email: cib...@redhat.com >>> Twitter: davsclaus >>> Blog: http://davsclaus.com >>> Author of Camel in Action: http://www.manning.com/ibsen >>> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@redhat.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen
