BTW.: I don't see any value in the SNAPSHOT site. Users will always want to look at the site of the release, since that is what they are using.
2014-07-25 11:34 GMT+02:00 Benedikt Ritter <[email protected]>: > You're probably refering to the Dependency Information report, I've posted > on the other thread. I think it would be sufficient to configure it to use > the latest release (we already have this information in the properties used > by the build plugin). > > Creating a documentation branch feels like a lot of overhead to me. I'm > curious whether git would make this any easier, since working with branches > is said to be easier in git. > > Benedikt > > > 2014-07-23 1:07 GMT+02:00 Gary Gregory <[email protected]>: > > Hi All: >> >> Snapshots site are useless to users and somewhat useful to developers. >> >> It is nice to be able to republish a site at will to fix documentation >> bugs >> _without_ releasing a new version. >> >> But, this is usually done by dragging along a SNAPSHOT version of >> everything. >> >> What to do? >> >> We need to publish the current version of a component and keep it there, >> as >> is. What about doc only changes? What if those fixes are Javadoc fixes? >> Does not seem doable. >> >> We could have, on the side a SNAPSHOT site. >> >> That means two sites: RELEASE and SNAPSHOT. >> >> Thoughts? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
