Harald Meyer wrote:
Hi,
available x.Why do you want to do that? What do you want to achieve?the idea is to allow users to specify "partial" version numbers for dependencies (at least for internal dependencies). So "0.8" means download the artifact in version "0.8.x" with the highest
The functionality should be similar to snapshots. If a newversion of
the dependency appears, it should be used in future builds.Why don't you simlpy replace the 0.8 version within the repo then and archive the minors (0.8.x, 0.8.y) elsewhere?
I tried a similar approach first: Version 0.8 was a symbolic link that was
updated every time a new minor version was released. The problem with this
approach is that if somebody already downloaded a 0.8 version he will not
get future 0.8 versions as Maven won't download newer versions.
yup. You would have to declare the 0.8 dependency as 0.8-SNAPSHOT. Then it would check the timestamp of the remote file and download it if it's new.
That's the only workaround I know about. Non snapshots are never downloaded when in the local repository.
Milos Kleint
Best regards, Harald Meyer
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
