I have done the next step in setting up some services on our zone.
There is now a forrestbot running there to build the current "seed site".
Just the cron side of forrestbot for the moment. The forrestbot web interface
is the next thing to set up.
There are cron jobs to automatically refresh the
I don't know if it helps us in any way, but this patch was just now
added to cocoon trunk:
http://issues.apache.org/bugzilla/show_bug.cgi?id=35435
getSitemapURIPrefix() in Request
"... returns the URI-prefix corresponding to the mount point
of the sitemap"
-David
Ferdinand Soethe wrote:
> David Crossley wrote:
>
> > Ah, you a misunderstanding how it works.
>
> > You are subscribed to the list as one address. When you send from
> > another address, then the message sits is a queue waiting for
> > a human moderator to approve it. I had to do that for this m
Ross, one of the "cleanup" steps in the release process is to
remove the "release candidate" files from your people.apache.org
We don't want google giving people unreleased products.
-David
Ross Gardler wrote:
> Ross Gardler wrote:
> >David Crossley wrote:
> >>
> >>* jars without accompanying licenses.
> >>* jar filenames not following our naming convention.
> >
> >Sorry, Lazy, I will sort that out today.
>
> Done.
Thanks, that is quite an effort i know.
> A couple of jars are stil
Woops, i had this prepared days ago but forgot to send.
Anil Ramnanan wrote:
> Here are the current deliverables that I intend to produce for the
> Summer of code project and the order in which I intend to do them. I was
> wondering if there were any comments from the community on them.
Good id
Paul Glezen wrote:
Thanks, Ross, for the timely response. I wonder if we should remove the
references to status.xml that appear in the default "forrest seed"
command. In particular the
/status.xml # List of project developers
and
- Edit status.xml and src/documentation/skinconf.xml
Otherwis
Thanks, Ross, for the timely response. I wonder if we should remove the references to status.xml that appear in the default "forrest seed" command. In particular the
/status.xml# List of project developers
and
- Edit status.xml and src/documentation/skinconf.xml
Otherwise, I suspec
Paul Glezen wrote:
Hi Folks,
I just downloaded Forrest 0.7 and run my first "forrest seed".
Everything seems fine except that I'm missing the status.xml in the root
directory. I also noticed it seems to be missing in my
/main/fresh-site directory. Am I missing something here?
In 0.7 we have
Hi Folks,
I just downloaded Forrest 0.7 and run my first "forrest seed". Everything seems fine except that I'm missing the status.xml in the root directory. I also noticed it seems to be missing in my /main/fresh-site directory. Am I missing something here?
Thanks,
- Paul
Paul Glezen
Consult
I've been struggling for a couple of days with this. I wonder if someone
can help.
I need to convert an HTML document to XDoc (or XHTML2). I'm using the
html2document.xsl in our SVN as a starting point but am thinking that it
may be a dead end.
The problem is that the html2document.xsl style
[ http://issues.apache.org/jira/browse/FOR-557?page=all ]
Ross Gardler closed FOR-557:
Resolution: Fixed
All patches applied - thanks
> Update Site for Forrest Plugin
> --
>
> Key: FOR-557
> URL: http://iss
jars in tools/eclipse/...lib need accompanying license
---
Key: FOR-561
URL: http://issues.apache.org/jira/browse/FOR-561
Project: Forrest
Type: Task
Versions: 0.8-dev
Reporter: David Crossley
Fix
Ross Gardler wrote:
> Just before the release of 0.7 Forrest and Lenya agreed to collaborate
> on Doco. It was suggested that we create a joint list for collaboration
> (or a virtual list).
>
> I'm not familiar with the processes for getting a list set up can
> someone point me in the right dir
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
...
I have relicensed the code (I was the previous Copyright holder) and
committed it to
tools/eclipse/plugins/org.apache.forrest.eclipse.servletEngine
This resolves issue FOR-503
...
I see a number of issues:
* duplicate
Nicola Ken Barozzi wrote:
I would be even more supportive if Lenya and Cocoon adopt the Maven one,
so that we would have a single format for all these projects.
You mean http://maven.apache.org/maven2/site.html ?
And here is how we could do it instead:
http://www.apa
Ross Gardler wrote:
Is it a plugin? Why not tools/eclipse/updatesite?
Yes, that would be better.
If we do that then we need to set SVN to ignore the folders that
building the site will create. It would be easier to have the build
process output the generated files in our build directory, th
Thorsten Scherler wrote:
> On Wed, 2005-06-29 at 08:43 +0200, Nicola Ken Barozzi wrote:
...
>>I would be even more supportive if Lenya and Cocoon adopt the Maven one,
>>so that we would have a single format for all these projects.
>
> You mean http://maven.apache.org/maven2/site.html ?
>
> The se
Remove duplicate jars from eclipse plugins
--
Key: FOR-560
URL: http://issues.apache.org/jira/browse/FOR-560
Project: Forrest
Type: Task
Versions: 0.8-dev
Reporter: Ross Gardler
Fix For: 0.8-dev
tools/eclipse
David Crossley wrote:
Ross Gardler wrote:
The Burrokeet project (http://www.burrokeet.org) voted to donate their
Servlet controller code to the Apache Forrest project. This code
improves the way that the Forrest Eclipse Plugin starts and stops the
Jetty server. The Forrest code was already de
Just before the release of 0.7 Forrest and Lenya agreed to collaborate
on Doco. It was suggested that we create a joint list for collaboration
(or a virtual list).
I'm not familiar with the processes for getting a list set up can
someone point me in the right direction and I'll get onto it.
Sorry I didn't realise this had been cross-posted and so I only replied
to one list (whatever happened to the joint list idea? - I'll start a
new thread)
Original Message
Date: Wed, 29 Jun 2005 10:57:45 +0100
From: Ross Gardler <[EMAIL PROTECTED]>
To: dev@lenya.apache.org
Tho
[ http://issues.apache.org/jira/browse/FOR-388?page=all ]
Ross Gardler updated FOR-388:
-
Fix Version: 0.7
Description:
At present Forrest will attempt to download plugins even if they are available
in src form in the local filesystem as part of an SVN c
Anil Ramnanan wrote:
Ross Gardler wrote:
Having done this it seems to me that the site.xml file should now go
in the root of our tools/eclipse folder and therefore reuse the
plugins/features from tools/eclipse/plugins and tools/eclipse/features.
Is this correct?
I would suggest another fo
On Wed, 2005-06-29 at 08:43 +0200, Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
> > Gregor J. Rothfuss wrote:
> >
> >> Ross Gardler wrote:
> >>
> >>> Well, in that case I would avoid EMF for this instance and we need
> >>> not consider whether site.xml is to have a DTD or not. Just a tree
> >>>
Has anybody considered internationalization of Forrest admin and user
interfaces yet? Is there a concept on how to translate Forrest's and
Coccon's messages into other languages?
--
Ferdinand Soethe
26 matches
Mail list logo