On 7/30/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
...While following the infrastructure@ mailing list I get the impression that
all
projects that use Confluence (+ Pier's autoexport plugin) as CMS, don't put
the
docs into SVN
It would be interesting to verify this, maybe via [EMAIL
Bertrand Delacretaz wrote:
On 7/30/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
...While following the infrastructure@ mailing list I get the impression that
all
projects that use Confluence (+ Pier's autoexport plugin) as CMS, don't put the
docs into SVN
It would be interesting
While following the infrastructure@ mailing list I get the impression that all
projects that use Confluence (+ Pier's autoexport plugin) as CMS, don't put the
docs into SVN.
AFAIU it is still an ASF rule (at least I haven't heard something different) but
OTOH it prevents us from
Reinhard Poetz pisze:
While following the infrastructure@ mailing list I get the impression
that all projects that use Confluence (+ Pier's autoexport plugin) as
CMS, don't put the docs into SVN.
AFAIU it is still an ASF rule (at least I haven't heard something
different) but OTOH
Simone Gianni wrote:
Hi all,
I was playing with the profiler when I noticed the way the
ProfilingXMLPipe works. Every component is given the opportunity to
stream its sax events, they are buffered in a DOM, the DOM is then used
(to display the intermediate XML and) to stream SAX events to the
David Crossley wrote:
David Crossley wrote:
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this. We will need
to set up re-directs now.
Here are files I used - attached
Vadim
/692.html
/bylaws-addendum.html
/developing/concepts/avalon.html
David Crossley wrote:
hepabolu wrote:
David Crossley wrote:
It seems that despite our concerns and attempts to address it
at the time, we still broke the URL space when publishing the
2.1 docs.
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this.
hepabolu wrote:
David Crossley wrote:
It seems that despite our concerns and attempts to address it
at the time, we still broke the URL space when publishing the
2.1 docs.
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this. We will need
to set
David Crossley wrote:
It seems that despite our concerns and attempts to address it
at the time, we still broke the URL space when publishing the
2.1 docs.
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this. We will need
to set up re-directs now.
It seems that despite our concerns and attempts to address it
at the time, we still broke the URL space when publishing the
2.1 docs.
Vadim, Helma, ... does anyone still have a list of the
filenames from when we investigated this. We will need
to set up re-directs now.
-David
Author: rgardler
[EMAIL PROTECTED] wrote:
Log:
Verified to be up-to-date in Daisy repository on
http://cocoon.zones.apache.org/daisy/
Removed:
cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/installing/index.xml
cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/installing/jars.xml
Got me
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
Log:
Verified to be up-to-date in Daisy repository on
http://cocoon.zones.apache.org/daisy/
Removed:
cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/installing/index.xml
Upayavira wrote:
Vadim Gritsenko wrote:
Probably release should have then snapshot of daisy docs, and docs
webapp should change accordingly.
Either include the docs from Daisy, or include the generated HTML. I'd
probably go with the latter. A shame that Cocoon can't, by itself,
generate
Upayavira wrote:
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
Log:
Verified to be up-to-date in Daisy repository on
http://cocoon.zones.apache.org/daisy/
Removed:
cocoon/branches/BRANCH_2_1_X/src/documentation/xdocs/installing/index.xml
14 matches
Mail list logo
