On Wed, Jun 15, 2011 at 09:31:24AM +0100, sebb wrote: > For components that use Nexus, it's trivial to use mvn deploy on a > SNAPSHOT release. > > This can be useful for developers to check that a patch solves their problem. > > However, snapshots should not be advertised to the general user > public, so should never be referenced from download pages, nor on the > user list. > > But AFAIK it would be OK to mention the snapshot on the JIRA issue. > > There are also some projects that use the CI servers to upload > snapshots. Not sure how that is done.
It would be nice to have a "latest" snapshot together with all snapshots that are supposed to solve a given issue. "latest" would be overwritten by the last issue snapshot. E.g. assuming that issue (MATH-799) is resolved, the following snapshots would be available: math-commons.MATH-774.jar math-commons.latest.jar -> math-commons.MATH-774.jar Then, later, when issue MATH-768 is resolved: math-commons.MATH-774.jar math-commons.MATH-768.jar math-commons.latest.jar -> math-commons.MATH-768.jar [Such a history might be useful to help users spot which change might have resulted in breaking something.] Best regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
