Gebhardt, Jörn wrote:
If I now build a project "projectB" that depends on the Snapshot version of project "projectA ", Maven looks into the central repository and overrides my just built and installed version with an older one from the central repository. My guess is that this happened because it compares the meta-information of the central repository with the "last modified" file system attribute of the projectA -1.0-SNAPSHOT.pom file.
This guess is wrong, the file's timestamp is not used for snapshot updates. Instead. the timestamp recorded in maven-metadata-*.xml files is used to determine the latest snapshot.
Is this an already known bug? If it is a bug, does there exist any workaround (e.g. tell the install plugin to change the "last modified" attribute of the POM when copying it into the local repository)?
Maven 3.0.1 has a bug in this regard which is fixed in 3.0.2. So if you can provide an example project that demonstrates the problem, please fill a bug in the isse tracker so we can take a closer look.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
