Le 11 déc. 05, à 16:37, juan a écrit :
...Aparently there is some problem with your server.
http://cocoon.zones.apache.org
I'm tied today, it would be good if someone could restart the services
according to
https://svn.apache.org/repos/private/committers/pmc/cocoon/
cocoon.zones.apache.org
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 12 December 05:02 AM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2005-12-12 05:02:10
... Rendering docs in
/export/home/
Hi:
While reviewing the javadocs, I found there is a link that is broken.
The content is there, but the linkrewriter is non-correrctly redirecting
the content.
Try:
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/xml/xlink/package-frame.html
I found the .htaccess file in /www/cocoon
dave- wrote:
Stefano Mazzocchi wrote:
Mark Lowe wrote:
Nice charts.. They assume that the same folk that are there at the
start of the start line are the same folk that are end or even perhaps
middle. Despite having a lot of respect for stefano's achievements and
the contribution that cocoon
Stefano Mazzocchi wrote:
Mark Lowe wrote:
Nice charts.. They assume that the same folk that are there at the
start of the start line are the same folk that are end or even perhaps
middle. Despite having a lot of respect for stefano's achievements and
the contribution that cocoon has made, I th
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 12 December 02:02 AM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2005-12-12 02:02:16
... Rendering docs in
/export/home/
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
Daniel Fagerstrom wrote:
It seem like we all agree about that the Cocoon core need to be
simplified, although we have different opinions about how to achieve it.
IMO it can be done in steps by refactoring of the trunk.
One of the complications with Cocoon is the environment abstraction:
o.a.c
Mark Lowe wrote:
Nice charts.. They assume that the same folk that are there at the
start of the start line are the same folk that are end or even perhaps
middle. Despite having a lot of respect for stefano's achievements and
the contribution that cocoon has made, I think the graphs are wrong,
o
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 11 December 11:02 PM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2005-12-11 11:02:08
... Rendering docs in
/export/home/
Il giorno 11/dic/05, alle ore 18:56, Daniel Fagerstrom ha scritto:
WDYT?
/Daniel
Know what? I proposed the same some time ago (I've tried digging out
the reference, but couldn't), so a big +1 from me.
Ugo
Jorg Heymans skrev:
Daniel Fagerstrom wrote:
...
The root of the problem lies somewhere in the current m2 poms from
excalibur. These have been automatically converted from the m1
project.xml files, so they are not using things like
provided where they should. This problem became very
apparen
Daniel Fagerstrom wrote:
I think that the problems is that there was a 2.0.2 release of the
xml-apis by mistake, don't know the story behind it, but see
http://www.apache.org/dist/java-repository/xml-apis/jars/. It should
have been 1.0.b2.
Several poms at the official maven repository have
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 11 December 08:02 PM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2005-12-11 08:02:15
... Rendering docs in
/export/home/
I think that the problems is that there was a 2.0.2 release of the
xml-apis by mistake, don't know the story behind it, but see
http://www.apache.org/dist/java-repository/xml-apis/jars/. It should
have been 1.0.b2.
Several poms at the official maven repository have dependencies of
2.0.2. This
It seem like we all agree about that the Cocoon core need to be
simplified, although we have different opinions about how to achieve it.
IMO it can be done in steps by refactoring of the trunk.
One of the complications with Cocoon is the environment abstraction:
o.a.c.environment.Request, Resp
I've just done a fresh build of trunk using m2, which failed somehow
because of problems with xml-apis, saying something like:
"This artifact has been relocated to xml-apis:xml-apis:1.0.b2."
And I also found references to it trying to get it from a URL at:
http://cvs.apache.org/maven-snapshot-
Hello,
Aparently there is some problem with your server.
http://cocoon.zones.apache.org
Best regards,
Juan
Joan
Baz
[EMAIL PROTECTED]
Adaptiva Sistemas, S.L.
http://www.adaptiva.es
Ball de Diables,
2
43205 – Reus – Spain
+34 676 702 569
Stefan Pietschmann wrote:
It's a new day and a new problem arises for me:
I want to notify my Avalon component when a session is created or
destroyed. I had previously written a simple HttpSessionListener which
I declared in web.xml. sessionCreated() and sessionDestroyed() get
invoked j
It's a new day and a new problem arises for me:
I want to notify my Avalon component when a session
is created or destroyed. I had previously written a simple HttpSessionListener
which I declared in web.xml. sessionCreated() and sessionDestroyed() get
invoked just as they should.
Now w
I've been wanting to add my 2 pence since stefano's "is cocoon
redundant" thread. I also admit i'm not a cocoon developer.
Nice charts.. They assume that the same folk that are there at the
start of the start line are the same folk that are end or even perhaps
middle. Despite having a lot of respe
21 matches
Mail list logo
