You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Antonio Gallardo <ag...@agssa.net> on 2004/06/14 22:51:54 UTC
Fixing forrest generation.....
Hi:
Sorry for the delay, I needed to make somethings at work. Anyway, there is
the fix:
Requisites:
Lastest forrest in CVS (it is the same as we tried today morning in CST).
Just delete the directory: $OJB_HOME/forrest/build
Full clean and rebuild, it must work now.
BTW, while checking the build.xml in OJB, I found the line 154:
<mkdir dir="${build.doc}"/>
is not needed at all, we can just remove this line.
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Brian McCallister wrote:
> Updated site =)
Brian, could you make a clean javadoc/forrest run please ? At least the
new javadoc stylesheet is missing.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Armin Waibel <ar...@apache.org>.
Antonio Gallardo wrote:
> Hi Armin:
>
> A recent CVS commit in forrest maybe solved the problem, please update it.
>
Nope, it doesn't. I think the fix was based on Krysalis style only.
It's a great pity, because IMO we need this feature urgently. Hope it
will be fixed in near future.
Thanks for the hint.
regards,
Armin
> Best Regards,
>
> Antonio Gallardo
>
> Armin Waibel dijo:
>
>>Antonio Gallardo wrote:
>>
>>
>>>Armin Waibel dijo:
>>>
>>>
>>>>Hi all,
>>>>
>>>>really big problem with new generated site. At the beginning of the
>>>>files no index was generated. This makes easy navigation impossible.
>>>>
>>>>old version
>>>>http://www.powaibel.de/ojb/ojb-style/docu/repository.html
>>>>
>>>>new version
>>>>http://db.apache.org/ojb/docu/repository.html
>>>
>>>
>>>Please check inside forrest.properties for a switch to get the "old"
>>>layout. I don't remember the name of it now.
>>
>>hmm, I think this is done in skinconf.xml with
>><toc max-depth="2" min-sections="1" location="page"/>
>>table of contents tag.
>>
>>We have set this tag. If I seed a new project with Forrest and use the
>>default skin, the toc is generated. If I use Tigris skin the toc was not
>>generated.
>>Bug in Tigris skin?
>>
>>regards,
>>Armin
>>
>>
>>
>>>Best Regards,
>>>
>>>Antonio Gallardo
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>>For additional commands, e-mail: ojb-dev-help@db.apache.org
>>>
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi Armin:
A recent CVS commit in forrest maybe solved the problem, please update it.
Best Regards,
Antonio Gallardo
Armin Waibel dijo:
> Antonio Gallardo wrote:
>
>> Armin Waibel dijo:
>>
>>>Hi all,
>>>
>>>really big problem with new generated site. At the beginning of the
>>>files no index was generated. This makes easy navigation impossible.
>>>
>>>old version
>>>http://www.powaibel.de/ojb/ojb-style/docu/repository.html
>>>
>>>new version
>>>http://db.apache.org/ojb/docu/repository.html
>>
>>
>> Please check inside forrest.properties for a switch to get the "old"
>> layout. I don't remember the name of it now.
>
> hmm, I think this is done in skinconf.xml with
> <toc max-depth="2" min-sections="1" location="page"/>
> table of contents tag.
>
> We have set this tag. If I seed a new project with Forrest and use the
> default skin, the toc is generated. If I use Tigris skin the toc was not
> generated.
> Bug in Tigris skin?
>
> regards,
> Armin
>
>
>>
>> Best Regards,
>>
>> Antonio Gallardo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Armin Waibel <ar...@apache.org>.
Antonio Gallardo wrote:
> Armin Waibel dijo:
>
>>Hi all,
>>
>>really big problem with new generated site. At the beginning of the
>>files no index was generated. This makes easy navigation impossible.
>>
>>old version
>>http://www.powaibel.de/ojb/ojb-style/docu/repository.html
>>
>>new version
>>http://db.apache.org/ojb/docu/repository.html
>
>
> Please check inside forrest.properties for a switch to get the "old"
> layout. I don't remember the name of it now.
hmm, I think this is done in skinconf.xml with
<toc max-depth="2" min-sections="1" location="page"/>
table of contents tag.
We have set this tag. If I seed a new project with Forrest and use the
default skin, the toc is generated. If I use Tigris skin the toc was not
generated.
Bug in Tigris skin?
regards,
Armin
>
> Best Regards,
>
> Antonio Gallardo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Antonio Gallardo <ag...@agssa.net>.
Armin Waibel dijo:
> Hi all,
>
> really big problem with new generated site. At the beginning of the
> files no index was generated. This makes easy navigation impossible.
>
> old version
> http://www.powaibel.de/ojb/ojb-style/docu/repository.html
>
> new version
> http://db.apache.org/ojb/docu/repository.html
Please check inside forrest.properties for a switch to get the "old"
layout. I don't remember the name of it now.
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Armin Waibel <ar...@apache.org>.
Hi all,
really big problem with new generated site. At the beginning of the
files no index was generated. This makes easy navigation impossible.
old version
http://www.powaibel.de/ojb/ojb-style/docu/repository.html
new version
http://db.apache.org/ojb/docu/repository.html
regards,
Armin
Thomas Dudziak wrote:
> Brian McCallister wrote:
>
>> Updated, though the API documention (javadoc) is broken.
>>
>>
>> I don't have time to look into it right now, unfortunately. If someone
>> can take the time to see why I keep getting rc6 docs in the forrest
>> site I'd appreciate it it.
>>
>> Ditto why the images don't work in the javadocs, and the title is broken.
>
>
> Hmm, works for me (fresh OJB CVS update with cleaned target/dist/doc
> folders, fresh checkout of Forrest). Javadoc is in place with new
> stylesheet and correct titles (with rc7 and all), and release-notes.txt
> is correct version from today 11:46. PDF looks all right except for the
> tables.
> I made only a slight change to the build.xml so that the 'website'
> target uses the top-level doc folder rather than the temporary
> ${build.dir}/doc.
>
> You're right though that Javadoc isn't using images for the inheritance
> 'graph' (right below the class name) but rather ascii characters.
> Strange, on my home computer this works (which is why I didn't use the
> Tigris <code> CSS style because the image that Javadoc uses is not
> transparent thus white on grey).
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Brian McCallister wrote:
> Updated, though the API documention (javadoc) is broken.
>
>
> I don't have time to look into it right now, unfortunately. If someone
> can take the time to see why I keep getting rc6 docs in the forrest
> site I'd appreciate it it.
>
> Ditto why the images don't work in the javadocs, and the title is broken.
Hmm, works for me (fresh OJB CVS update with cleaned target/dist/doc
folders, fresh checkout of Forrest). Javadoc is in place with new
stylesheet and correct titles (with rc7 and all), and release-notes.txt
is correct version from today 11:46. PDF looks all right except for the
tables.
I made only a slight change to the build.xml so that the 'website'
target uses the top-level doc folder rather than the temporary
${build.dir}/doc.
You're right though that Javadoc isn't using images for the inheritance
'graph' (right below the class name) but rather ascii characters.
Strange, on my home computer this works (which is why I didn't use the
Tigris <code> CSS style because the image that Javadoc uses is not
transparent thus white on grey).
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Brian McCallister <mc...@forthillcompany.com>.
Updated, though the API documention (javadoc) is broken.
I don't have time to look into it right now, unfortunately. If someone
can take the time to see why I keep getting rc6 docs in the forrest
site I'd appreciate it it.
Ditto why the images don't work in the javadocs, and the title is
broken.
Thanks,
Brian
On Jun 15, 2004, at 9:14 AM, Brian McCallister wrote:
> Something is really wonky with the build -- forrest was using an old
> release-notes and the javadocs seem to refuse to release the rc6 in
> the title.
>
> Will look into it, but need to work at the moment.
>
> -Brian
>
> On Jun 15, 2004, at 9:03 AM, Thomas Dudziak wrote:
>
>> Brian McCallister wrote:
>>
>>> I did update the properties file (note the tarball names) -- the
>>> release notes are independent of the build.properties version spec.
>>
>> Yup, Armin changed the release notes in CVS (version from 'final' to
>> 'rc7', some known issues explanation), and I added a stylesheet to
>> the Javadoc build process to make the API doc better fitting the rest
>> of the site.
>>
>> Tom
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Brian McCallister <mc...@forthillcompany.com>.
Something is really wonky with the build -- forrest was using an old
release-notes and the javadocs seem to refuse to release the rc6 in the
title.
Will look into it, but need to work at the moment.
-Brian
On Jun 15, 2004, at 9:03 AM, Thomas Dudziak wrote:
> Brian McCallister wrote:
>
>> I did update the properties file (note the tarball names) -- the
>> release notes are independent of the build.properties version spec.
>
> Yup, Armin changed the release notes in CVS (version from 'final' to
> 'rc7', some known issues explanation), and I added a stylesheet to the
> Javadoc build process to make the API doc better fitting the rest of
> the site.
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Brian McCallister wrote:
> I did update the properties file (note the tarball names) -- the
> release notes are independent of the build.properties version spec.
Yup, Armin changed the release notes in CVS (version from 'final' to
'rc7', some known issues explanation), and I added a stylesheet to the
Javadoc build process to make the API doc better fitting the rest of the
site.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Brian McCallister <mc...@forthillcompany.com>.
I did update the properties file (note the tarball names) -- the
release notes are independent of the build.properties version spec.
-Brian
On Jun 15, 2004, at 8:51 AM, Thomas Dudziak wrote:
> Brian McCallister wrote:
>
>> does the website ant task update this? I don't want to release
>> 1.0rc7.1 =)
>
> Nope, these are set in the build.properties ('# project name and
> version info'). And since you already released 1.0 final (at least
> according to the release-notes.txt on the website) ...
> So a simple clean rebuild should do the trick.
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Brian McCallister wrote:
> does the website ant task update this? I don't want to release
> 1.0rc7.1 =)
Nope, these are set in the build.properties ('# project name and version
info'). And since you already released 1.0 final (at least according to
the release-notes.txt on the website) ...
So a simple clean rebuild should do the trick.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Brian McCallister <mc...@forthillcompany.com>.
does the website ant task update this? I don't want to release 1.0rc7.1
=)
-Brian
On Jun 15, 2004, at 7:50 AM, Armin Waibel wrote:
> Hi Brian,
>
> do you think it is possible to replace the release-notes file on site?
> I made some significant changes.
>
> regards,
> Armin
>
> Brian McCallister wrote:
>
>> Updated site =)
>> -Brian
>> On Jun 14, 2004, at 5:25 PM, Antonio Gallardo wrote:
>>> Thomas Dudziak dijo:
>>>
>>>> Antonio Gallardo wrote:
>>>>
>>>>> Hi:
>>>>> Sorry for the delay, I needed to make somethings at work. Anyway,
>>>>> there
>>>>> is
>>>>> the fix:
>>>>>
>>>>> Requisites:
>>>>> Lastest forrest in CVS (it is the same as we tried today morning in
>>>>> CST).
>>>>>
>>>>> Just delete the directory: $OJB_HOME/forrest/build
>>>>
>>>>
>>>> Mhm, that's strange, I changed building so that forrest does not use
>>>> this directory anymore (it now builds in target/doc). I wonder why
>>>> it
>>>> interfered ?
>>>
>>>
>>> The interferece was because we were copying all the forrest dir to
>>> the new
>>> location. Including the "build/temp" dir, where forrest store some
>>> prebuilded stuff. Between the snapshot used before from some weeks
>>> ago and
>>> the lastest forrest CVS stuf, there was a very important change in
>>> forrest:
>>>
>>> The upgrade of Cocoon to 2.1.5 and it causes a lot of changes on the
>>> pregenerated temp files including a lot of changed libs. That is why
>>> the
>>> error was too weird and also explain why is so simple the solution
>>> to this
>>> problem.
>>>
>>> BTW, the titles are fixed as well as good rendered HTML pages, but
>>> not the
>>> PDF files. :(
>>>
>>> Anyway, it is better than we have now. ;-)
>>>
>>> I already posted on the forrest dev list about the problem on the PDF
>>> generation. Hopefully, someone can help us there. If not I will try
>>> tomorrow to check where is the problem with it.
>>>
>>> BTW, Is OJB using a customized forrest skin?
>>>
>>> Best Regards,
>>>
>>> Antonio Gallardo.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Armin Waibel <ar...@apache.org>.
Hi Brian,
do you think it is possible to replace the release-notes file on site?
I made some significant changes.
regards,
Armin
Brian McCallister wrote:
> Updated site =)
>
> -Brian
>
> On Jun 14, 2004, at 5:25 PM, Antonio Gallardo wrote:
>
>> Thomas Dudziak dijo:
>>
>>> Antonio Gallardo wrote:
>>>
>>>> Hi:
>>>> Sorry for the delay, I needed to make somethings at work. Anyway, there
>>>> is
>>>> the fix:
>>>>
>>>> Requisites:
>>>> Lastest forrest in CVS (it is the same as we tried today morning in
>>>> CST).
>>>>
>>>> Just delete the directory: $OJB_HOME/forrest/build
>>>
>>>
>>> Mhm, that's strange, I changed building so that forrest does not use
>>> this directory anymore (it now builds in target/doc). I wonder why it
>>> interfered ?
>>
>>
>> The interferece was because we were copying all the forrest dir to the
>> new
>> location. Including the "build/temp" dir, where forrest store some
>> prebuilded stuff. Between the snapshot used before from some weeks ago
>> and
>> the lastest forrest CVS stuf, there was a very important change in
>> forrest:
>>
>> The upgrade of Cocoon to 2.1.5 and it causes a lot of changes on the
>> pregenerated temp files including a lot of changed libs. That is why the
>> error was too weird and also explain why is so simple the solution to
>> this
>> problem.
>>
>> BTW, the titles are fixed as well as good rendered HTML pages, but not
>> the
>> PDF files. :(
>>
>> Anyway, it is better than we have now. ;-)
>>
>> I already posted on the forrest dev list about the problem on the PDF
>> generation. Hopefully, someone can help us there. If not I will try
>> tomorrow to check where is the problem with it.
>>
>> BTW, Is OJB using a customized forrest skin?
>>
>> Best Regards,
>>
>> Antonio Gallardo.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Brian McCallister <mc...@forthillcompany.com>.
Updated site =)
-Brian
On Jun 14, 2004, at 5:25 PM, Antonio Gallardo wrote:
> Thomas Dudziak dijo:
>> Antonio Gallardo wrote:
>>> Hi:
>>> Sorry for the delay, I needed to make somethings at work. Anyway,
>>> there
>>> is
>>> the fix:
>>>
>>> Requisites:
>>> Lastest forrest in CVS (it is the same as we tried today morning in
>>> CST).
>>>
>>> Just delete the directory: $OJB_HOME/forrest/build
>>
>> Mhm, that's strange, I changed building so that forrest does not use
>> this directory anymore (it now builds in target/doc). I wonder why it
>> interfered ?
>
> The interferece was because we were copying all the forrest dir to the
> new
> location. Including the "build/temp" dir, where forrest store some
> prebuilded stuff. Between the snapshot used before from some weeks ago
> and
> the lastest forrest CVS stuf, there was a very important change in
> forrest:
>
> The upgrade of Cocoon to 2.1.5 and it causes a lot of changes on the
> pregenerated temp files including a lot of changed libs. That is why
> the
> error was too weird and also explain why is so simple the solution to
> this
> problem.
>
> BTW, the titles are fixed as well as good rendered HTML pages, but not
> the
> PDF files. :(
>
> Anyway, it is better than we have now. ;-)
>
> I already posted on the forrest dev list about the problem on the PDF
> generation. Hopefully, someone can help us there. If not I will try
> tomorrow to check where is the problem with it.
>
> BTW, Is OJB using a customized forrest skin?
>
> Best Regards,
>
> Antonio Gallardo.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Armin Waibel <ar...@apache.org>.
Thomas Dudziak wrote:
>> BTW, Is OJB using a customized forrest skin?
>
>
> I was under the impression that we're using a standard Tigris skin, but
> Armin will know exactly.
It's standard Tigris + some CSS changes for code, codefrag, ... elements
and color settings in skinconf.xml.
For example in orginal Tigris skin the code sections are not emphasised
we use a grey background.
regards,
Armin
> At least the CSS stylesheets are from Tigris because I'm using them
> right now to change the stylesheet for Javadoc.
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Antonio Gallardo wrote:
> The interferece was because we were copying all the forrest dir to the new
> location. Including the "build/temp" dir, where forrest store some
> prebuilded stuff.
Ah, I see.
> Between the snapshot used before from some weeks ago and
> the lastest forrest CVS stuf, there was a very important change in
> forrest:
>
> The upgrade of Cocoon to 2.1.5 and it causes a lot of changes on the
> pregenerated temp files including a lot of changed libs. That is why the
> error was too weird and also explain why is so simple the solution to this
> problem.
>
> BTW, the titles are fixed as well as good rendered HTML pages, but not the
> PDF files. :(
I've noticed the HTML pages are better now :-) We should have everybody
check all browsers (and PDF readers ?) out there to see whether it's
good now.
> I already posted on the forrest dev list about the problem on the PDF
> generation. Hopefully, someone can help us there. If not I will try
> tomorrow to check where is the problem with it.
That'd be great! PDF without borders is way ugly.
> BTW, Is OJB using a customized forrest skin?
I was under the impression that we're using a standard Tigris skin, but
Armin will know exactly.
At least the CSS stylesheets are from Tigris because I'm using them
right now to change the stylesheet for Javadoc.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Antonio Gallardo <ag...@agssa.net>.
Thomas Dudziak dijo:
> Antonio Gallardo wrote:
>> Hi:
>> Sorry for the delay, I needed to make somethings at work. Anyway, there
>> is
>> the fix:
>>
>> Requisites:
>> Lastest forrest in CVS (it is the same as we tried today morning in
>> CST).
>>
>> Just delete the directory: $OJB_HOME/forrest/build
>
> Mhm, that's strange, I changed building so that forrest does not use
> this directory anymore (it now builds in target/doc). I wonder why it
> interfered ?
The interferece was because we were copying all the forrest dir to the new
location. Including the "build/temp" dir, where forrest store some
prebuilded stuff. Between the snapshot used before from some weeks ago and
the lastest forrest CVS stuf, there was a very important change in
forrest:
The upgrade of Cocoon to 2.1.5 and it causes a lot of changes on the
pregenerated temp files including a lot of changed libs. That is why the
error was too weird and also explain why is so simple the solution to this
problem.
BTW, the titles are fixed as well as good rendered HTML pages, but not the
PDF files. :(
Anyway, it is better than we have now. ;-)
I already posted on the forrest dev list about the problem on the PDF
generation. Hopefully, someone can help us there. If not I will try
tomorrow to check where is the problem with it.
BTW, Is OJB using a customized forrest skin?
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Fixing forrest generation.....
Posted by Thomas Dudziak <to...@first.fhg.de>.
Antonio Gallardo wrote:
> Hi:
> Sorry for the delay, I needed to make somethings at work. Anyway, there is
> the fix:
>
> Requisites:
> Lastest forrest in CVS (it is the same as we tried today morning in CST).
>
> Just delete the directory: $OJB_HOME/forrest/build
Mhm, that's strange, I changed building so that forrest does not use
this directory anymore (it now builds in target/doc). I wonder why it
interfered ?
> Full clean and rebuild, it must work now.
It does, I just checked out Forrest and there were no problems.
> BTW, while checking the build.xml in OJB, I found the line 154:
>
> <mkdir dir="${build.doc}"/>
>
> is not needed at all, we can just remove this line.
I'll remove it.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org