'build test' should run validate-config target
Key: FOR-542
URL: http://issues.apache.org/jira/browse/FOR-542
Project: Forrest
Type: Improvement
Components: Compile
Reporter: Thorsten Scherler
Fix For:
- I will write a document explaining the details of how the
documentation structure is meant to work and howtos on inserting
new information and create new releases.
= Liste of changes: This is an unsolved issue that we will need to
solve before the release. I'd like to move them up to the project
level as it has all changes of all versions and doesn't really
belong in 'versioned docs' but if somebody wants to make the
effort we could
= old dtds that are no longer required for active versions
(document-v11 and -v12) but might still be wanted on special
occasions. I'm thinking about having a separate folder or folders
for these where we move them as a first step of their retirement
while still keeping them
...
Create a plugins task for ANT
-
Key: FOR-535
URL: http://issues.apache.org/jira/browse/FOR-535
...
The ant file for loading and mounting plugins is horribly
complex now that we are using versioned plugins. I've used
lots of if elements and mutable
Ross Gardler wrote:
Like I've said before, tell me what projectInfo plugin does not do that
you need and I will make it do it.
Thanks. I was hoping you'd offer :-)
But let people decide if we really need that.
We could put 'Changes' back to the new 'docs' directory (still to
be
Now that the release candidate is done, all of you have a chance to
check it out and voice your opinions while I am going to be quiet for
a couple of days doing some other work and going kayaking until the
weekend.
Before I do, I want to say a huge thank you to David for tirelessly
(to be taken
- To keep things simple we have started out by making a lot of
documentation 'versioned' thus increasing the volume of our
site-author-directory quite a bit.
In the upcoming weeks I'd like to go through the documentation and
move items like the dtd-documentation back into a
Ferdinand Soethe wrote:
We could put 'Changes' back to the new 'docs' directory (still to
be re-created) and it would work just fine. I'd be happy with that so
why put more work into it. Unless sbdy else wants version specific
changes.
Sorry, I just looked it up again and have to correct
Ross Gardler wrote:
It is a good idea to clearly mark deprecated DTD's. In fact I would go a
step further and say we move them to a deprecatedDTD plugin. This would
be an internal plugin. This would leave only active DTD's in core so new
users will not be tempted to use deprecated ones.
Ferdinand Soethe wrote:
- To keep things simple we have started out by making a lot of
documentation 'versioned' thus increasing the volume of our
site-author-directory quite a bit.
In the upcoming weeks I'd like to go through the documentation and
move items like the dtd-documentation
Juan Jose Pablos a écrit :
Cyriaque Dupoirieux wrote:
Just want to add that some dtdV1todtdV2.xsl files already exist in
$FORREST_HOME/main/webapp/resources/stylesheets.
It could be a good idea to maintain these kind of files in order to
migrate old forrest site...
For instance, we
Juan Jose Pablos a écrit :
Cyriaque Dupoirieux wrote:
Hi,
I am looking for the xmap which generates the linkmap.html.
Thank you,
maybe main/webapp/linkmap.xmap is what are you looking for :-)
Okay, I am not used to cocoon pipelines, I tried to do the following :
* I changed
Hi,
I did a quick test of the 0.7rc1. Please find my findings. Let me know
if you want to have the testresults in a different format or noted
somewhere else.
test of Forrest 0.7 rc1
testing environment:
Hardware: Acer Travelmate 4001 WLMI running Ubuntu Hoary
#uname -a
Linux acer-ubuntu
On Tue, 2005-06-14 at 10:53 +0200, Ferdinand Soethe wrote:
- I will write a document explaining the details of how the
documentation structure is meant to work and howtos on inserting
new information and create new releases.
Nice work, David and Ferdinand.
Thanks for doing
Nico Veenkamp wrote:
Hi,
I did a quick test of the 0.7rc1. Please find my findings. Let me know
if you want to have the testresults in a different format or noted
somewhere else.
test of Forrest 0.7 rc1
testing environment:
Hardware: Acer Travelmate 4001 WLMI running Ubuntu Hoary
Cyriaque Dupoirieux wrote:
Juan Jose Pablos a écrit :
Cyriaque Dupoirieux wrote:
Hi,
I am looking for the xmap which generates the linkmap.html.
Thank you,
maybe main/webapp/linkmap.xmap is what are you looking for :-)
Okay, I am not used to cocoon pipelines, I tried to do the
Sub tabs not working in default view
Key: FOR-543
URL: http://issues.apache.org/jira/browse/FOR-543
Project: Forrest
Type: Bug
Components: Views
Versions: 0.8
Reporter: Ross Gardler
Priority: Minor
Fix
Ferdinand Soethe wrote:
Before I do, I want to say a huge thank you to David for tirelessly
(to be taken literally) working with me on the restructuring when he
had other things to do and mopping up my many mistakes.
There was mutual mopping up.
Of course thanks to you too. We had a big job
19 matches
Mail list logo
