metadata-updater is changing lastUpdating timestamp when it shouldn't

This is a bit of a trivial 'bug' and the result is not harmfull, but I think the metadata-updater should not change data that is valid.

As far as I could find the lastUpdated field is the timestamp on which the metadata was last updated, so should not be touched in this case.

During scanning, some (~200) maven-metadata.xml files are updated in my repository .
The metadata being updated is:
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>com.informatica.profiling.services</groupId>
<artifactId>profiling-model-persist</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20070213.050129</timestamp>
<buildNumber>79</buildNumber>
</snapshot>
<lastUpdated>20070213050130</lastUpdated>
</versioning>
</metadata>

After update the lastUpdated field is changed to 20070213050129:
<lastUpdated>20070213050129</lastUpdated>

As far as I could find the lastUpdated field is the timestamp on which the metadata was last updated, so should not be touched in this case.

Scanlog:
2007-10-05 14:38:41,043 [pool-2-thread-1] DEBUG org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - Sending to consumer: metadata-updater
2007-10-05 14:38:41,090 [pool-2-thread-1] INFO org.apache.maven.archiva.consumers.KnownRepositoryContentConsumer:metadata-updater - Updated metadata: com/xxx/profiling/services/profiling-model-persist/1.0-SNAPSHOT/maven-metadata.xml
2007-10-05 14:38:46,356 [pool-2-thread-1] INFO org.apache.maven.archiva.consumers.KnownRepositoryContentConsumer:metadata-updater - Updated metadata: com/xxx/profiling/services/profiling-model-persist/maven-metadata.xml