The only reason I see is to have all documents together with the code
and all the other documents. I think this could be a great benefit.
Oliver
Am 17.08.15 um 13:50 schrieb Tresch, Anatole :
Hi all
the only thing we need is some tooling that
- checks out during deploy the current site from SVN
- update the corresponding directories for docs, examples and javadocs with the
related content generated by the normal maven build
- check in the changes to SVN so they are staged.
So basically I don’t see (yet) either why we should now jump on the site train.
The things described are no so complicated, e.g. it can be done by some ant
tasks or even with some tweaked site settings. So I would propose to evaluate
our options before just choosing a tool ;)
Perhaps I have some time next days to see what is possible and how things can
be done more easily...
Cheers,
Anatole
-----Original Message-----
From: Oliver B. Fischer [mailto:o.b.fisc...@swe-blog.net]
Sent: Sonntag, 16. August 2015 17:55
To: dev@tamaya.incubator.apache.org
Subject: Re: Where is the website?
IMHO Maven site would perfect for us as it offers us an easy way to
manage our documentation and all the other stuff. That a lot of projects
use other tools is easy to understand as the default Maven site looks ugly.
As we do not have so many people currently contributing to Tamaya Maven
Site would be a light weight solution for us.
WDYT?
Oliver
Am 16.08.15 um 17:23 schrieb Werner Keil:
Can you point to any Apache projects incubating or not, who use Reflow for
their "modern" look?
Werner
On Sun, Aug 16, 2015 at 5:19 PM, Werner Keil <werner.k...@gmail.com> wrote:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf
