Hi, we're using an internal repository manager (Artifactory) for storing our internal artifacts. Local builds always have a version number of '99999999' (instead of SNAPSHOT, there are good reasons for that) -- we're only using simple numbers for versioning internal artifacts, A.B.C -like versioning does not make sense in our case, as we never do major and minor releases. If the developer changes two dependent projects (A and B, A depends on B) locally, then - he builds and installs B, therefore version 99999999 will be installed into the local repo - he builds A, which references artifact B version LATEST, therefore it should -- in theory -- use artifact B version 999999999. However, it always downloads the latest deployed version from the repository manager, and uses that one. Artifact B's metadata files in the local repository: - maven-metadata-local correctly references version 99999999 - maven-metadata-releases references the versions which are deployed to the repository manager
How could I force mvn to pick up the latest installed version from the local repository instead of the latest deployed version (with _lower_ version number)? Thanks, Mate
