I updated features.xml to use pom dependency versions via variables.
There are no hard-coded version numbers left there now.
Amichai
On 07/07/2013 10:46 PM, Christian Schneider wrote:
Hi Amichai,
generally the feature should use the same versions as the pom. Using a
variable for this is a good idea. For most versions we already have
version properties but not for all. I think for the zookeeper upgrade
I checked the multibundle distro but forgot the karaf feature.
I hope we can improve this process in the future. I would like to
create a maven plugin that creates the multi bundle distro from the
karaf feature file.
Christian
Am 07.07.2013 15:58, schrieb A. Rothman:
Hi,
I just noticed in features.xml the ZooKeeper version was left behind
at 3.3.1, so I fixed it to use the same version as the pom (using the
pom variable).
In addition, the feature specifies jdom version 1.1_3, whereas the
pom specifies 1.1.2_1. I wasn't sure why the discrepancy here (in the
opposite direction) or if it's ok to just upgrade the pom and fix the
features to use the same variable as the pom, so I left it as it is
for now, but would be happy to fix if you guys say it's ok.
Amichai