From: Tim P. <tim...@ou...> - 2009-06-15 16:18:45
|
On Monday 15 Jun 2009 16:01:17 Olaf Hartig wrote: > On Monday 15 June 2009 15:56:42 Tim Pizey wrote: > > [...] > > SNAPSHOT is a Maven special keyword. > > What is special about SNAPSHOT is that it will go off and get the very > > latest build. > > Just to understand this. Does "will go off and get the very latest build" mean > Maven fetches the latest versions of all required libraries before compiling > the project? No, I am being unclear because I am not certain of the details. Maven has two types of repository, those where 'snapshot versions' are allowed and those where they are not. The difference is that in addition to the file's version the file also has a date incorporated into its name. If I deploy a.jar at version 1.3 the file name in a non-snapshot repository will be a-1.3.jar. However if I deploy to a snapshot repository then the file name will be, for example: http://paneris.net/maven2/de/fuberlin/wiwss/ng4j/ng4j/0.9-SNAPSHOT/ng4j-0.9-20090606.175554-1.jar I think that this is artefact id + version + date + time + serial So when a dependency has the special tag SNAPSHOT then Maven goes and checks the remote repository for the most recent version, even if it has a locally cached copy which matches on version number alone. > > Using POST is fine, but is new to this project I think. > > Yes it is new - remember, we did not had a version build property before you > suggested to have one. I added the POST prefix because I assumed having > version "0.9.1" after the release would not be right. > However, I'm still unsure whether I should also adjust the version in pom.xml > to "POST-0.9.1". Certainly in the POM and probably in build.xml we should use SNAPSHOT. cheers Tim |