I have been thinking alot lately about SNAPSHOTS and how to best utilize them. I think I perhaps have misunderstood them and I wanted to see what kind of responses I get from the community, particularly from the guys at Sonatype.
I took a look at Nexus (which I am using as a good example of a Maven project) to see what kind of versioning it uses. Users of Nexus generally only ever see released versions of it. ie: version 1.2.0.1, 1.2.0.2, 1.3.0 and so on and so forth. Does the Nexus dev team ever create a release of Nexus that is meant for internal purposes only? For instance, do you have a verification team and if so, how do you distribute a build that you want the verification team to test? I suspect your verificaton is done on a SNAPSHOT version, which I believe is one of my big misconceptions of what SNAPSHOTS are meant for. I have always thought of SNAPSHOTS as a version that is strictly meant to track nightly builds or builds between developers. However, now I am not so sure. Is it reasonable to work with a SNAPSHOT in your local repostiory, do a number of unit tests and sanity on that SNAPSHOT and then deploy a version of that SNAPSHOT to your corporate maven repository to share with the rest of the company/community so that they can use it and test against it? A SNAPSHOT is time stamped so a consumer can always know exactly what version they are using. Am I off my rocker? (well, I supose thats a seperate question ;-)) --- Todd Thiessen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
