Oh, I see... How do you think this could affect the release? Are you aware if there's any check for build.number somewhere? Only rpc, spark and spark_dmv were including this file inside their swcs in the whole sdk. The release process will still use the build.number to update all the Version.as files and create the rsls.
The swcs produced pass the new checkintests that Alex fixed yesterday. I'll try to run some mustella checks just in case. If we do need to include them, then we need to find a way around it, because as Alex noted, the include-file directive in the ant task overrides the one inside the config file, and I think having them inside the config file makes the new Falcon functional tests to fail (because the file is created through the ant target). Cheers, Chema 2012/12/8 Justin Mclean <jus...@classsoftware.com> > Hi, > > > Remove version.properties include-file directive from rpc, spark and > spark_dmv as conflicts with compile-config.xml and is currently unused > You might want to double check that it not used in the release build. I > think that the version number is used when generating the RSLs. > > Justin
