Re: JDBC website help !

On 06/01/2012 02:20 AM, Dave Cramer wrote:
> Hi Mikko,
>
> Thanks for taking the time to figure this out. I ran out of time.
>
> I still get a few broken links
>
> <broken-links>
> <link message="/home/davec/projects/jdbc/www/src/documentation/content/xdocs/development
> (Is a directory)">development/</link>
> <link message="/home/davec/projects/jdbc/www/src/documentation/content/xdocs/documentation
> (Is a directory)">documentation/</link>

Looking at the last two lines of the scripts/buildSite.sh I believe it looks like those are supposed to be missing
and because the script copies public and private javadocs to those locations. And at lest for me the links work
in the generated site.

> <link message="/home/davec/projects/jdbc/www/src/documentation/content/xdocs/documentation/84/index.xml
> (No such file or directory)">documentation/84/index.html</link>

I'm not sure why one of these should magically appear.

> <link message="No pipeline matched request: favicon.ico
> at<map:mount> -
> file:///home/davec/tools/apache-forrest-0.9/main/webapp/./sitemap.xmap:609:76">favicon.ico</link>

This is definitely not mandatory.

> <link message="/home/davec/projects/jdbc/www/src/documentation/content/xdocs/images..jpg
> (No such file or directory)">images/.jpg</link>

This goes away if you replace in status.xml two places where it says
<action dev="jurka"> with <action dev="jurka" type="add">

> </broken-links>
>
> Did you solve these as well ?

I think some broken links can be allowed as long as the main functionality is there, and for example
the images..jpg broken link has been there for ages. So lets not try to make it perfect.

In the status.xml we should try to document what changes went into the jdbc driver since the
last site update. But even that can be done by someone at a later time after we know that the site
can actually be successfully updated.

-Mikko

> On Thu, May 31, 2012 at 5:56 PM, Mikko Tiihonen
> <mikko(dot)tiihonen(at)nitorcreations(dot)com> wrote:
>> On 05/31/2012 04:11 PM, Dave Cramer wrote:
>>>
>>> I've spent a few days trying to build the website. Currently it is
>>> using apache forrest to create the website. I have been unable to
>>> build it and I don't really have any more time to work on it. I'm
>>> also not inclined to spend a whole lot of time to learn Forrest.
>>>
>>> Do we have anyone with Forrest expertise ?
>>
>>
>> I had never before heard of it. But I think I might have managed to build
>> the site now.
>>
>> I used the latest 0.9 release of Forrest. And after googling a bit it seems
>> that
>> generating the changes and todo that you were missing out of the status.xml
>> at the root
>> has been moved to a plugin. After you enable it by adding:
>>
>> project.required.plugins=org.apache.forrest.plugin.input.projectInfo
>>
>> to the forrest.properties the changes& todo are properly generated.
>>
>>
>> In addition to actually run the ant target doc on the git checkout
>> succesfully
>> I had to add to build.local.properties:
>> docbook.dtd=/usr/share/sgml/docbook/xml-dtd-4.2
>> docbook.stylesheet=/usr/share/sgml/docbook/xsl-stylesheets-1.76.1/xhtml-1_1/docbook.xsl
>>
>> + add latest xalan-2 jar to classpath.
>>
>>
>>> Alternatively should we look at another way to build the website ?
>>> Possibly use the same infrastructure as the main www.postgresql site ?
>>> Or another simple way ?
>>>
>>> Suggestions (and volunteers) welcome.
>>
>>
>> I think the jdbc project does not have extra resources to maintain its own
>> web site presence.
>>
>> Either:
>> 1) ask if www.postgresql could embed jdbc content somewhere in their site -
>> after a volunteer migrates the current site content to their infrastructure
>> 2) keep using forrest, but move the building of the site to git repository
>> too - and script it so that it actually works properly
>> - instead of requiring the site-developer to download and maintain all
>> release source codes it could just fetch then from the git repository
>> - add all required defines to build.properties so that it works at least
>> on some machine and provides examples for the next person on what to tune
>> - automate loading and installing of forrest if required
>>
>> -Mikko
>>
>> --
>> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-jdbc