Automated build for forrest-seed FAILED
Log attached.
--
Forrestbot run ended at 12 August 03:55 AM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-12 03:55:33
... Rendering docs in
/expor
Automated build for forrest-seed FAILED
Log attached.
--
Forrestbot run ended at 12 August 02:55 AM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-12 02:55:22
... Rendering docs in
/expor
Ferdinand Soethe wrote:
> David Crossley wrote:
>
> > In the previous thread, Ross and i had strong opinions
> > about not making a distinction between "us and them".
> > We are all "developers". Some of us (mainly the committers)
> > make extra effort to do the tasks that keep the project
> > flo
That is because the dispatcher has now a dependency to the inputModule.
I just updated the zone server. We will know whether it is fixed in 3
hours.
salu2
El vie, 11-08-2006 a las 20:56 +,
[EMAIL PROTECTED] escribió:
> Automated build for forrest-sample-2 FAILED
> Log attached.
>
>
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 11 August 08:56 PM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-11 08:56:09
... Rendering docs in
/e
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 11 August 05:56 PM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-11 05:56:08
... Rendering docs in
/e
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 11 August 02:56 PM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-11 02:56:08
... Rendering docs in
/e
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 11 August 11:56 AM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-11 11:56:08
... Rendering docs in
/e
[
http://issues.apache.org/jira/browse/FOR-742?page=comments#action_12427495 ]
Ross Gardler commented on FOR-742:
--
I closed this issue quite some time ago, but David re-opened it, I can't quite
remember why. I think it was becasue we needed to
le 11/08/2006 12:14 Ross Gardler a écrit :
David Crossley wrote:
Gav wrote:
Yep, sorry about that.
No worries, just helping to get you going smoothly.
Another thing. Please try to add any relevant Jira issue
numbers to the commit log message.
For anyone who doesn't know why it may be
David Crossley wrote:
Gav wrote:
Yep, sorry about that.
No worries, just helping to get you going smoothly.
Another thing. Please try to add any relevant Jira issue
numbers to the commit log message.
For anyone who doesn't know why it may be worth a reminder...
Adding FOR-200 to a co
Thorsten Scherler wrote:
El jue, 10-08-2006 a las 21:10 +0100, Ross Gardler escribió:
Thorsten Scherler wrote:
El jue, 10-08-2006 a las 04:09 +, [EMAIL PROTECTED] escribió:
Author: crossley
Date: Wed Aug 9 21:09:40 2006
New Revision: 430235
URL: http://svn.apache.org/viewvc?rev=43023
[
http://issues.apache.org/jira/browse/FOR-742?page=comments#action_12427486 ]
Cyriaque Dupoirieux commented on FOR-742:
-
Can I close this, because I don't know what I can do more than the fallback
mecanism which is now in place :
Forres
[ http://issues.apache.org/jira/browse/FOR-919?page=all ]
Cyriaque Dupoirieux closed FOR-919.
---
Resolution: Fixed
The release notes actions are retrieved with a key filtering on the @importance.
The let you define your own contexts and see them in the r
[ http://issues.apache.org/jira/browse/FOR-918?page=all ]
Cyriaque Dupoirieux closed FOR-918.
---
Resolution: Fixed
Done,
To use the translation, just copy the
src/documentation/translation/ProjectInfoMessages[locale].xml to your project
translation dir
[ http://issues.apache.org/jira/browse/FOR-595?page=all ]
Cyriaque Dupoirieux closed FOR-595.
---
Fix Version/s: 0.8-dev
Resolution: Fixed
> Hard-coded project name in input.projectinfo plugin
> ---
>
[
http://issues.apache.org/jira/browse/FOR-595?page=comments#action_12427483 ]
Cyriaque Dupoirieux commented on FOR-595:
-
Oliver, Now it's OK,
The plugin gets the value of skinconf/project-name.
BTW, the solution of Gavin was a good work
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest-test has an issue affecting its community integration.
This issue affects
[ http://issues.apache.org/jira/browse/FOR-918?page=all ]
Cyriaque Dupoirieux updated FOR-918:
Description:
Some may be suprised to see several english words in their projectInfo pages.
We should use the i18n transformer and dedicated catalogues to s
[ http://issues.apache.org/jira/browse/FOR-595?page=all ]
Cyriaque Dupoirieux reassigned FOR-595:
---
Assignee: Cyriaque Dupoirieux
> Hard-coded project name in input.projectinfo plugin
> ---
>
>
[ http://issues.apache.org/jira/browse/FOR-595?page=all ]
Work on FOR-595 started by Cyriaque Dupoirieux.
> Hard-coded project name in input.projectinfo plugin
> ---
>
> Key: FOR-595
> URL: http://issues.apache.o
[ http://issues.apache.org/jira/browse/FOR-919?page=all ]
Work on FOR-919 started by Cyriaque Dupoirieux.
> Release Notes do not use keys to retrieve important changes
> ---
>
> Key: FOR-919
> URL: http:/
Release Notes do not use keys to retrieve important changes
---
Key: FOR-919
URL: http://issues.apache.org/jira/browse/FOR-919
Project: Forrest
Issue Type: Improvement
Compone
[ http://issues.apache.org/jira/browse/FOR-918?page=all ]
Work on FOR-918 started by Cyriaque Dupoirieux.
> Site-visible message strings are hard coded and not i18n in projectInfo plugin
> --
>
> Key:
Site-visible message strings are hard coded and not i18n in projectInfo plugin
--
Key: FOR-918
URL: http://issues.apache.org/jira/browse/FOR-918
Project: Forrest
Iss
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest has an issue affecting its community integration.
This issue affects 1 pr
Automated build for forrest-sample-2 FAILED
Log attached.
--
Forrestbot run ended at 11 August 08:56 AM
Using Forrest 0.8-dev
Forrestbot administrator: Forrest developers
--
[echo]
... Forrest render START 2006-08-11 08:56:07
... Rendering docs in
/e
El vie, 11-08-2006 a las 09:42 +0200, Cyriaque Dupoirieux escribió:
> Excellent,
>
jeje, I knew you would like it. ;)
> These kind of improvement are very important.
Very much agree.
> We need to have an overview of what is done by each component to be able
> to improve the code quality and t
David Crossley wrote:
> In the previous thread, Ross and i had strong opinions
> about not making a distinction between "us and them".
> We are all "developers". Some of us (mainly the committers)
> make extra effort to do the tasks that keep the project
> flowing. I have not yet heard any justif
Excellent,
These kind of improvement are very important.
We need to have an overview of what is done by each component to be able
to improve the code quality and the performance.
(Actually, we need a design dossier ;-) )
Salutations,
Cyriaque,
le 11/08/2006 09:10 [EMAIL PROTECTED] a écrit :
30 matches
Mail list logo
