It may not publish anything to "Apache Snapshot" repo as it is set up right now, but we have a Jenkins that continuously builds trunk of several projects.
If any of them differs by more than just fixing a typo it should no longer be called "1.0.0" as it is now, otherwise the content of the JAR or other files generated would be different from the official 1.0.0 release. On Thu, Jul 17, 2014 at 5:52 PM, Reza <[email protected]> wrote: > Right, if we do CI where our artifacts are being automatically published > for other devs or to a larger audience, then it would be appropriate to > label the release with a SNAPSHOT as to not get confused with an official > release. I dont think this effects versioning in general, its more like > what Bertrand said, "work in progress". > > > http://stackoverflow.com/questions/5901378/what-exactly-is-a-maven-snapshot-and-why-do-we-need-it > > > > ________________________________ > From: Bertrand Delacretaz <[email protected]> > To: "[email protected]" < > [email protected]> > Sent: Thursday, July 17, 2014 11:36 AM > Subject: Re: Jira > > > On Thu, Jul 17, 2014 at 5:28 PM, Werner Keil <[email protected]> > wrote: > > > The document does not seem to use the "-SNAPSHOT" notion... > > > > Semantic versioning is meant for modules which are released - it is of > course fine to use -SNAPSHOT for work in progress. > > > -Bertrand >
