jlabbe-processia / mxupdate

Automatically exported from code.google.com/p/mxupdate
1 stars 1 forks source link

Version check broken #176

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. enable version chek and version export within the propeties
2. export an attribut to file
3. write a version text (e.g. "$Rev: 1$") into the VERSION header section below 
the ~~~~ line.
4. import the CI file into Enovia
5. change the version text (e.g. "$Rev: 2$")
6. import the CI file into Enovia. You will see a message inticating an update 
to "null", but the CI is updated and the correct version text is put into the 
version property.
7. now import the CI file into Enovia again, now without a change. Angain the 
message about an update to "null" appears and the CI is updated. That should 
not be the case, as the versions are equal.

What version of the product are you using? On what operating system?
MxUpdate 0.10.0
Windows 7

Please provide any additional information below.

From looking into the code, it seems the version check is done in UpdateUtils 
before the files header information is read in AbstractPropertObject. So the 
property value is compared to null.

Original issue reported on code.google.com by bu...@mbudde.com on 19 Sep 2013 at 9:02

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:31