On Monday, August 11, 2003, at 06:36 pm, Noel J. Bergman wrote:
It has been even questioned the need to publish javadocs that can be
done locally by users. More I think of it, more I agree, as doing it
for all Apache projects is an awful lot of duplication and disk space.
If I am working with a
On Tuesday, Aug 12, 2003, at 08:46 Europe/Rome, James Strachan wrote:
On Monday, August 11, 2003, at 08:54 pm, Noel J. Bergman wrote:
The only disagreement is - should all this dynamically generated
stuff
go into CVS or not. It seems silly to put it into CVS - since its
trivial to regenerate t
On Tuesday, August 12, 2003, at 02:52 pm, Noel J. Bergman wrote:
James Strachan wrote:
Noel J. Bergman wrote:
One of the reasons for putting dynamically generated artifacts into
CVS is that in the event of a recovery situation, CVS is on one
server, and the web sites are on another, so recovery c
On Monday, Aug 11, 2003, at 21:05 Europe/Rome, Daniel F. Savarese wrote:
In message <[EMAIL PROTECTED]>, "Noel J.
Bergman" w
rites:
If I am working with a package, e.g., Avalon, I might not have the
javadocs
or sources local. I often find references in the javadocs via
Google, which
can be qui
Rodent of Unusual Size wrote:
James Strachan wrote:
The only disagreement is - should all this dynamically generated stuff
go into CVS or not. It seems silly to put it into CVS - since its
trivial to regenerate the site at any point using Maven. Its worse than
saying lets check every version of
James Strachan wrote, On 11/08/2003 13.50:
...
Please do not publish the site directly to the server as we use the
incubator-site CVS for better oversight. We could change this, of
course, but ATM this is the way it's meant to be.
Is there any way around this restriction? Its just so easy to publ
James Strachan wrote:
> Noel J. Bergman wrote:
> > One of the reasons for putting dynamically generated artifacts into
> > CVS is that in the event of a recovery situation, CVS is on one
> > server, and the web sites are on another, so recovery can be
> > relatively quick. It is unreasonable to as
James Strachan wrote:
>
> The only disagreement is - should all this dynamically generated stuff
> go into CVS or not. It seems silly to put it into CVS - since its
> trivial to regenerate the site at any point using Maven. Its worse than
> saying lets check every version of a jar into CVS.
we
> The only disagreement is - should all this dynamically generated stuff
> go into CVS or not. It seems silly to put it into CVS - since its
> trivial to regenerate the site at any point using Maven. Its worse than
> saying lets check every version of a jar into CVS.
One of the reasons for puttin
James Strachan wrote, On 11/08/2003 12.31:
...
I'm wondering if it'd be OK to create a directory (say) inside the
incubator website tree. e.g.
/www/incubator.apache.org/projects/geronimo/...
then I can update this website automatically every day from CVS.
Incubator projects can create their webs
On Monday, August 11, 2003, at 08:54 pm, Noel J. Bergman wrote:
The only disagreement is - should all this dynamically generated stuff
go into CVS or not. It seems silly to put it into CVS - since its
trivial to regenerate the site at any point using Maven. Its worse
than
saying lets check ever
Hi,
James Strachan wrote:
I'd have thought a simple file backup of such things would do? If the
backup gets trashed, the site would eventually be updated by a quick
ping to the PMCs.
Not only would a file backup do but it is surely an
essential safeguard against certain risks. May as
well re-us
In message <[EMAIL PROTECTED]>, "Noel J. Bergman" w
rites:
>If I am working with a package, e.g., Avalon, I might not have the javadocs
>or sources local. I often find references in the javadocs via Google, which
>can be quite helpful. Before any decision to not publish javadocs were to
>be take
On Monday, August 11, 2003, at 12:29 pm, Nicola Ken Barozzi wrote:
James Strachan wrote, On 11/08/2003 12.31:
...
I'm wondering if it'd be OK to create a directory (say) inside the
incubator website tree. e.g.
/www/incubator.apache.org/projects/geronimo/...
then I can update this website automat
> It has been even questioned the need to publish javadocs that can be
> done locally by users. More I think of it, more I agree, as doing it
> for all Apache projects is an awful lot of duplication and disk space.
If I am working with a package, e.g., Avalon, I might not have the javadocs
or sou
15 matches
Mail list logo
