My Mistake- I was deploying distributions, not jars. The jar:deploy-snapshot creates the sym links and the index file.
Luciano -----Original Message----- From: Rafal Krzewski [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 8:43 AM To: Maven Users List Subject: Re: How adaptable is Maven's version system? Moretti, Luciano (MED) wrote: > I hate to disagree, as I'm a complete Newbie, but as I asked the > question, originally, I should comment on what I found- > > When you do a dist:snapshot-deploy or a jar:snapshot-deploy the archive > created has a timestamp on it (down to the Second it was created IIRC.) > You can have multiple snapshots deployed (I've got multiple created at > the moment) Unless something is badly broken you should also get artifact-SNAPSHOT.jar in the group directory, that is either a copy of the timestamped jar that you've just deployed, or a symlink to that file. The term 'snapshot version' means the most recent of the 'timestamped versions'. In the current setup this should always be available as artifact-SNAPSHOT.jar file/symlink. > I don't know how it works to pull the jar down, but I expect that it > checks the date tag and pulls down the most recent. Only artifact-SNAPSHOT.jar is checked/downloaded ATM. HTTP does not support directory listings (web server do support listings, but it's optional and not standarized) and FTP does not provide file timestamps, so our best bet at discovering artifact versions is maintaining a metadata file for each artifact in the group directory, that would contain filename, timestamp and checksum for each deployed version of the artifact. R. --------------------------------------------------------------------- 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]
