Resolving of an extension artifact from a maven repository seems to cause unexpected persistence of its POM information

To reproduce the issue on 3.2 XWiki:

1) Deploy an extension having a (release) POM with a dependency on org.xwiki.commons:xwiki-commons-component-default:3.3-SNAPSHOT (yes this extension is not referring the correct core version, this was a mistake we want to fix)
2) Try to resolve this extension, EM correctly detect the version issue and refuse to install:
C org.xwiki.commons:xwiki-commons-component-default (jar) (3.2 was 3.3-SNAPSHOT)
3) Re-deploy the same extension, fixing the version of the dependency to 3.2
4) Try to resolve again this extension, EM still report a dependency on 3.3-SNAPSHOT
In _/aether-repository/path/to/your/extension.pom, the file is still the old one, and has been persisted
5) Restart the wiki
6) Try to resolve again this extension, EM still report a dependency on 3.3-SNAPSHOT
Since the file in _/aether-repository/path/to/your/extension.pom, is still there with the old information
7) Delete the file _/aether-repository/path/to/your/extension.pom
8) Try to resolve again this extension, EM report now the correct dependency on 3.2:
C org.xwiki.commons:xwiki-commons-component-default (jar) (3.2)

Since this is a redeploy of a release, this is not really unexpected, but Thomas tells me that it is not even expected to persist this information in the way EM is suppose to works.