David Crossley wrote:
Ron Blaschke wrote:
Thorsten Scherler wrote:
Ron Blaschke wrote:
I think this is a problem with the plugin. If you look at the
0.8/org.apache.forrest.plugin.output.inputModule.zip there's a file
lib/org.apache.forrest.plugin.output.inputModule.jar. It contains
Ross Gardler wrote:
On 20/04/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
only for test i put org.rblasch.forrest.plugin.input.pod.PodGenerator
in the list of the plugin.
Thanks for this.
Many thanks to both of you for bringing this to my attention.
No locationmap provided for plugin
Ross Gardler wrote:
On 20/04/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi,
Just for test I put
org.apache.forrest.plugin.output.inputModule in the list of
plugin in the forrest.properties file.
Note I use the java version j2sdk1.4.2_03.
When trying to reach the index.html, the
[
http://issues.apache.org/jira/browse/FOR-591?page=comments#action_12357381 ]
Ron Blaschke commented on FOR-591:
--
This is a Cocoon issue.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36162
MaxMemory needs increasing
Ross Gardler wrote:
Ron Blaschke wrote:
Ross Gardler wrote:
Most things are straightforward. I'm only puzzled by the mix of input
plugin (ie, take data from the profiler data store and render it) and
internal plugin (ie, profile stuff and store results in profiler data
store). Can a plugin
David Crossley wrote:
David Crossley wrote:
Ron Blaschke wrote:
Ron Blaschke wrote:
[snip]
NN Components(Role)Average time Lastest times
1 file ([1]) 213 ms 30 ms30 ms 581 ms
2 idgen 6 ms 10 ms 0 ms10 ms
3 xinclude
Monday, August 29, 2005, 5:21:07 PM, David Crossley wrote:
Ron Blaschke wrote:
David Crossley wrote:
Currently, I am wondering about three things:
- How can the top level pipes be replaced with their profiling
counterparts, without too much hassle?
Perhaps this is possible using
[ http://issues.apache.org/jira/browse/FOR-572?page=all ]
Ron Blaschke updated FOR-572:
-
Attachment: step1_profiling.patch
This patch adds partial support for profiling through Cocoon pipelines.
You still need to replace the /standard pipes
Friday, August 26, 2005, 9:23:38 AM, David Crossley wrote:
Ron Blaschke wrote:
[snip profiler stuff]
Some Forrest developers definitely want to see these
numbers and do want to get their hands dirty with Cocoon.
There must be a lot that we can do to speed it up, e.g.
tune our cache; more
Sunday, August 28, 2005, 5:55:07 PM, Ron Blaschke wrote:
Sunday, August 28, 2005, 2:37:03 PM, David Crossley wrote:
Ron Blaschke wrote:
David Crossley wrote:
I've started to look at things, and were able to look at the Cocoon
profiler things with forrest run in site-author/.
Here's a short
Monday, August 22, 2005, 12:57:34 PM, David Crossley wrote:
Diwaker Gupta wrote:
So here's what I have right now:
o I can do a simple ./build.sh jar.debug -- this creates a debug version
of
Forrest. When you next run Forrest, the data will be automatically logged.
Where and how and
: Any
Reporter: Ron Blaschke
Priority: Minor
The Simplified Docbook plugin references its stylesheets via
map:transform
src={forrest:plugins}/org.apache.forrest.plugin.input.simplifiedDocbook/resources/stylesheets/sdocbook2document.xsl
/
in input.xmap.
This works with the unversioned
Thursday, August 18, 2005, 4:57:49 PM, David Crossley wrote:
Ron Blaschke wrote:
[snip]
Unfortunately, very little showed up. Here's what I did.
I ran a CPU profile on both revisions, which wasn't very helpful at
all. Nothing interesting showed up. chaperon seems to eat a
significant
Thursday, August 18, 2005, 5:58:54 PM, David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Ron Blaschke wrote:
Thought for the future when this is sorted out. Can we create a new test
target that will do this profiling for us?
That way, each time we upgrade a dependency we can
[
http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318705 ]
Ron Blaschke commented on FOR-572:
--
I reported the issue to Cocoon.
Possible Memory Leak with LinkRewriterTransformer
http://issues.apache.org/bugzilla/show_bug.cgi?id=36162
Thursday, August 11, 2005, 11:24:55 PM, Ross Gardler wrote:
Ron Blaschke wrote:
I did a quick comparison of Forrest revision 231407 (before Cocoon
update) and revision 230867 (somewhere near HEAD).
Ron, this work you are doing is fantastic. I don't know how you can call
it quick, it seems
Thursday, August 11, 2005, 4:21:50 AM, David Crossley wrote:
Ron Blaschke wrote:
I've had another look at Forrest's memory issue, this time more
deeply. I still only understand parts of it, and hope someone can
help fill in the missing pieces.
Now, my question is: How do you guys usually
Wednesday, August 10, 2005, 11:35:10 AM, Ross Gardler wrote:
Cyriaque Dupoirieux wrote:
Just a question to svn experts :
svn update returns :
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)
Do you know how I have locked a file ?
I've had another look at Forrest's memory issue, this time more
deeply. I still only understand parts of it, and hope someone can
help fill in the missing pieces.
The problem seems to originate at the LinkRewriteTransformer. Through
one way or the other, a single XMLFileModule is used. This
Sunday, July 31, 2005, 4:48:25 AM, David Crossley wrote:
Ron Blaschke wrote:
Second, there are over 180 XML DOM documents
(org.apache.xerces.dom.DocumentImpl) eating about 29MB. They are
referenced by an instance of
org.apache.cocoon.components.modules.input.XMLFileModule.
These documents
I've taken a quick glimpse at Forrest's memory usage, using the
lovely Yourkit Java Profiler (http://www.yourkit.com/).
I did the following: I ran forrest site in site-author/, and made a
snapshot, quite at the end of the run. Note that I have only limited
understanding of Forrest's and Cocoon's
[
http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314204 ]
Ron Blaschke commented on FOR-547:
--
Sorry about the link, looks like it got truncated.
Yes, the issue still exists with rc3. The simple workaround is to call
forrest init
[
http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314224 ]
Ron Blaschke commented on FOR-547:
--
Should I tackle this issue? You probably have more important things to worry
about. ;-)
Plugins are not installed when calling forrest
: Core operations
Versions: 0.7-dev
Environment: Windows XP, SP2
Ant 1.6.5
Forrest 0.7rc1
Reporter: Ron Blaschke
Priority: Minor
I have an Ant script, which imports forrest.build.xml. When calling the site
target with a missing plugin, the install fails. But forrest init-plugins
Friday, June 17, 2005, 11:01:40 PM, Ross Gardler wrote:
Ron Blaschke wrote:
Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
My forrest.properties says this:
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
org.apache.forrest.plugin.input.simplifiedDocbook
I
[
http://issues.apache.org/jira/browse/FOR-546?page=comments#action_12313971 ]
Ron Blaschke commented on FOR-546:
--
Sorry, should have been more specific. I am using the docbook stylesheets
(http://docbook.sourceforge.net/projects/xsl/index.html), and my
Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
Ron Blaschke wrote:
Unable to retrieve the ${plugin.name} plugin.
Two noteworthy things: Calling forrest init-plugins installs the
plugin sucessfully. And the error message says ${plugin.name},
instead of the real name of the plugin
Monday, June 13, 2005, 5:33:36 PM, Ross Gardler wrote:
Ron Blaschke wrote:
Sunday, June 12, 2005, 11:38:26 PM, Ross Gardler wrote:
Ron Blaschke wrote:
I am wondering if I made a mistake, and the URL should refer to the
directory only, like the others do, i.e.
url=http://www.rblasch.org
I haven't had time to dig into this in detail, but I hope someone
familiar with plugins will help me fill in the missing pieces.
I tried to build some site with the new 0.7rc1, which contains
simplified docbook documents. The site built successfully, but the
pages were empty (shouldn't this
Sunday, June 12, 2005, 11:38:26 PM, Ross Gardler wrote:
Ron Blaschke wrote:
I've taken a look at the plugins.xml, and the pod-input entry's URL
refers directly to the ZIP, i.e.
url=http://www.rblasch.org/projects/pod-input/org.rblasch.forrest.plugin.input.pod.zip;
I am wondering if I made
Saturday, June 11, 2005, 1:44:39 PM, Ross Gardler wrote:
Ron Blaschke wrote:
Friday, June 10, 2005, 11:02:52 AM, Ross Gardler wrote:
Please note that the Plugin system has been upgraded to allow versioned
plugins.
I'll upgrade the pod-input plugin as soon as I find time for it, which
should
Friday, April 22, 2005, 12:10:19 PM, Ross Gardler wrote:
In preparation for the 0.7 release of Forrest all plugins have now been
renamed to conform to our naming conventions.
I've also changed the name of my pod-input plugin to match the naming
convention.
The new fully qualified name will be
Sunday, January 2, 2005, 11:45:19 PM, Ross Gardler wrote:
Ron Blaschke wrote:
- Libraries
Yesterday, I committed support for libraries, but it is not documented
yet (perhaps you could add a section to the docs). Update your version
of Forrest with svn up, you can then include libraries
Monday, January 3, 2005, 8:58:40 PM, Ross Gardler wrote:
Ron Blaschke wrote:
Monday, January 3, 2005, 4:32:55 PM, Ron Blaschke wrote:
Sunday, January 2, 2005, 11:45:19 PM, Ross Gardler wrote:
Ron Blaschke wrote:
If there is a strong enough use case for such functionality I do not
think
Monday, January 3, 2005, 8:49:05 PM, Ross Gardler wrote:
Ron Blaschke wrote:
- forrest validate-xdocs
Validation is done by Forrest itself, all source documents in the
project are validated when the site is built using forrest site. There
is (should be?) no need for plugins to handle validation
35 matches
Mail list logo
