[
http://issues.apache.org/jira/browse/FOR-635?page=comments#action_12318971 ]
David Crossley commented on FOR-635:
Maybe i wasn't being clear. When forrest sees a URI that begins with
images/*.* then it uses main/webapp/resources.xmap to look first in
Just a reminder that our zone is working.
The Forrest demos there are still very minimal.
Anyway, there is at least something useful now working.
The home page now describes what is available so far:
http://forrest.zones.apache.org/
Basically it is updating the trunk every hour
and reporting
At the moment we do everything on the PMC private list
and only announce the new PMC member at the very end.
We do this ...
1) Vote and frank discussion in private.
2) If successful, then invite them.
after they accept, then do:
3) Advise them about next steps, ask for Contributor
License
David Crossley wrote:
Now all that waiting causes problems, e.g. Cyriaque's case
had successful vote, but we cannot yet announce it to the
dev list.
I didn't follow Cyriaque's case closely so I'm not sure what problem
this creates, could you explain this please.
It would be better if we
Ferdinand Soethe wrote:
David Crossley wrote:
Now all that waiting causes problems, e.g. Cyriaque's case
had successful vote, but we cannot yet announce it to the
dev list.
I didn't follow Cyriaque's case closely so I'm not sure what problem
this creates, could you explain this
Thanks for that thread. :)
salu2
On Wed, 2005-08-10 at 13:46 +1000, David Crossley wrote:
The answer is: very rarely.
http://forrest.apache.org/guidelines.html#actions
Votes are mainly for the following purposes:
1) Adoption of a new codebase.
2) Official releases.
3) New PMC
David Crossley wrote:
It would be better if we could announce them to dev@ list
at step 3 and just say that there are more procedural steps
which will take some time.
+1
However there are two potential problems there:
What if the new person refused to submit the CLA?
I cannot see why - it
On 8/17/05, Ross Gardler [EMAIL PROTECTED] wrote:
David Crossley wrote:
It would be better if we could announce them to dev@ list
at step 3 and just say that there are more procedural steps
which will take some time.
+1
However there are two potential problems there:
What if
There seems to be a couple of problems with transforming
xhtml-document.
Placing the document below as xhtml-test.html in the xdocs directory of a
freshly seeded forrest I will only see menues and tabs, not the
content of the page.
Calling it as body-xhtml-test.html everything looks fine so I
The pipeline match above assumes that your cocoon:/body-{0} is valid
to our *internal* format.
Your example is not conform to the internal format that means that you
first have to apply a transformation yourFormat2xdocs.
Thorsten Scherler wrote:
The pipeline match above assumes that your cocoon:/body-{0} is valid
to our *internal* format.
Yes I understand that. And I would if this was a new format to
support. But XHTML is supposed to work when I name it .html (See my
question to the user list).
Your example
Ferdinand Soethe wrote:
There seems to be a couple of problems with transforming
xhtml-document.
I found at least one of my mistakes:
!--pipeline that marries the docs in the root dir with the skin to produce
html--
map:match pattern=*.html
map:aggregate element=site
Ferdinand Soethe wrote:
Thorsten Scherler wrote:
The pipeline match above assumes that your cocoon:/body-{0} is valid
to our *internal* format.
Yes I understand that. And I would if this was a new format to
support. But XHTML is supposed to work when I name it .html (See my
question to the
Forrests SVN checkout is too large. One way of making it smaller is by
moving the eclipse tools directory out of trunk (10Mb).
Since devs working on the eclipse tools do so independantly of Forrest
this makes sense. In fact, in the new instructions I am writing for
setting up the eclipse
Daisy Repository Browser
-
Key: FOR-636
URL: http://issues.apache.org/jira/browse/FOR-636
Project: Forrest
Type: New Feature
Components: Tool: Eclipse config
Versions: 0.8-dev
Reporter: Anil Ramnanan
This is a plugin that
[ http://issues.apache.org/jira/browse/FOR-636?page=all ]
Anil Ramnanan updated FOR-636:
--
Attachment: daisyPlugin.zip
Daisy Repository Browser
Daisy Repository Browser
Key: FOR-636
URL:
Problem solved or rather 'gone away'. After updating to today's version
of Forrest and freshly seeding the site XHTML is supported as
expected.
Probably picked a bad time to seed the last one.
Thanks for your input.
--
Ferdinand Soethe
[
http://issues.apache.org/jira/browse/FOR-636?page=comments#action_12319063 ]
Ross Gardler commented on FOR-636:
--
Sorry I can't apply this patch, there are a number of issues, mostly legal:
Please ensure all license files are included with your patch and
On 8/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: crossley
Date: Tue Aug 16 19:15:58 2005
New Revision: 233106
URL: http://svn.apache.org/viewcvs?rev=233106view=rev
Log:
Clarify what we mean by commit-then-review.
Modified:
Ross Gardler wrote:
Forrests SVN checkout is too large. One way of making it smaller is by
moving the eclipse tools directory out of trunk (10Mb).
Anils new daisy plugin adds another 2.5 Mb...
Since devs working on the eclipse tools do so independantly of Forrest
this makes sense. In fact,
Inserting an html document into a project
-
Key: FOR-637
URL: http://issues.apache.org/jira/browse/FOR-637
Project: Forrest
Type: Test
Components: XML grammars validation
Versions: 0.7
Environment: Windows XP
[ http://issues.apache.org/jira/browse/FOR-637?page=all ]
Ross Gardler closed FOR-637:
Resolution: Invalid
Assign To: Ross Gardler
Please use the user mailing list to discuss how to use Forrest. The issue
tracker is for reporting bugs and
[
http://issues.apache.org/jira/browse/FOR-637?page=comments#action_12319091 ]
Ross Gardler commented on FOR-637:
--
Oops, sorry, to fast, I answered a question you didn't ask - not very helful.
To have the page display when you click the button you simply
Tim Williams wrote:
Ross Gardler wrote:
David Crossley wrote:
However there are two potential problems there:
What if the new person refused to submit the CLA?
I cannot see why - it doesn't take away any of
their rights.
If someone does refuse then that would lead to an
Folks,
Since the past 2 days, I've been getting this:
$ forrest site
X [0] linkmap.html BROKEN:
javax.xml.transform.TransformerException: Empty expression!
With $forrest run, I get:
Message: null
Description: No details available.
Sender:
25 matches
Mail list logo
