You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Mark Struberg <st...@yahoo.de> on 2016/03/21 13:00:30 UTC
docu cleanup
Hiho!
It took me almost the whole the last week, but now the openjpa doc of trunk is available again (think it was broken for over a year now).
http://openjpa.staging.apache.org/documentation.html
There is only a minor problem left now:
the structure of the single-html doesn’t correctly point to the css.
To reproduce what I mean simply run
$> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
Then look at zip
$> unzip -l ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
Our current document structure is
docs/
├── docbook
│ ├── manual
│ │ ├── appendices.html
│ │ ├── ch13s02.html
│ │ ├── ch13s03.html
│ │ ├── ch13s04.html
│ │ ├── ch29s04.html
│ │ ├── css
│ │ │ └── docbook.css
│ ├── manual.html
│ └── manual.pdf
├── javadoc
└── schema
My question is:
Currently the manual.html (full single-page html) cannot find the docbook.css as it is in manual/css/docbook.css.
Should be move the manual.html into the manual subfolder?
Or should we copy over the css folder for it?
LieGrue,
strub
Re: docu cleanup
Posted by Jody Grassel <fy...@gmail.com>.
How does one determine what level of java, maven, is being used on buildbot?
On Wed, Jun 15, 2016 at 3:40 PM, Mark Struberg <st...@yahoo.de.invalid>
wrote:
> Might be as simple as that it doesn’t work with the installed Java or
> Maven version on buildbot?
>
> LieGrue,
> strub
>
>
> > Am 15.06.2016 um 22:37 schrieb Mark Struberg <st...@yahoo.de>:
> >
> > That doesn’t look good…
> >
> > https://ci.apache.org/builders/openjpa-2.2.x-docs
> >
> >
> >
> >> Am 15.06.2016 um 22:35 schrieb Mark Struberg <st...@yahoo.de>:
> >>
> >>
> >> Let’s start with the most obvious.
> >>
> >> I went through all the ‚HTML manual links on
> http://openjpa.apache.org/documentation.html
> >>
> >> Only a few of them are broken
> >> * OpenJPA 1.0.5-SNAPSHOT (rest of 1.0.x works fine)
> >> * OpenJPA 1.2.4-SNAPSHOT (rest of 1.2.x works fine)
> >> * OpenJPA 1.3.0-SNAPSHOT (weird, there are no docs for the 1.3.0
> release? Should we remove it at all?)
> >>
> >> Basically all snapshot links are dead :(
> >>
> >> I _assume_ they should be hosted here:
> https://ci.apache.org/projects/openjpa/
> >> But only the trunk part is properly filled.
> >> I remember that the whole buildbot stuff was broken for at least 1
> year++ and I fixed trunk when I did the 2.4.1 release.
> >> We need to investigate what’s wrong with the other jobs.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> >>> Am 15.06.2016 um 17:30 schrieb Jody Grassel <fy...@gmail.com>:
> >>>
> >>> Pretty much all of the releases other than 2.4.x and trunk. Looking
> at
> >>> http://openjpa.apache.org/documentation.html I see 2.3.x-SNAPSHOT,
> >>> 2.2.x-SNAPSHOT, 2.1.x-SNAPSHOT, 2.0.x-SNAPSHOT, 1.3.x-SNAPSHOT,
> >>> 1.2.x-SNAPSHOT, and 1.0.x-SNAPSHOT as having broken links. Looking at
> the
> >>> builder for 2.2.x (
> >>>
> https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/317/steps/compile/logs/stdio
> >>> ) and the errors in them, I suspect a few changes that went into
> >>> trunk./2.4.x need to be back ported to those branches. I was
> experimenting
> >>> locally, looking at what changes had gone into trunk, but haven't
> cracked
> >>> the problem yet.
> >>>
> >>> On Wed, Jun 15, 2016 at 5:13 AM, Mark Struberg
> <st...@yahoo.de.invalid>
> >>> wrote:
> >>>
> >>>> Can you point me to the docs which are still broken?
> >>>> Might be as easy as a sed replace probably.
> >>>>
> >>>> LieGrue,
> >>>> strub
> >>>>
> >>>>
> >>>>> Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
> >>>>>
> >>>>> What were the steps involved in fixing the 2.4.x docs, so we can
> restore
> >>>>> documentation for earlier versions?
> >>>>>
> >>>>> On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <
> >>>> rmannibucau@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> If we can't change the css path for manual.html I would copy the css
> >>>>>> instead of copying manual.html to keep the structure hierarchic.
> >>>>>>
> >>>>>> Romain Manni-Bucau
> >>>>>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
> >>>>>>
> >>>>>>
> >>>>>> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> >>>>>>> Hiho!
> >>>>>>>
> >>>>>>> It took me almost the whole the last week, but now the openjpa doc
> of
> >>>>>> trunk is available again (think it was broken for over a year now).
> >>>>>>>
> >>>>>>> http://openjpa.staging.apache.org/documentation.html
> >>>>>>>
> >>>>>>> There is only a minor problem left now:
> >>>>>>> the structure of the single-html doesn’t correctly point to the
> css.
> >>>>>>>
> >>>>>>> To reproduce what I mean simply run
> >>>>>>>
> >>>>>>> $> mvn clean site install -DskipTests
> -Pjavadoc-profile,docbook-profile
> >>>>>>>
> >>>>>>> Then look at zip
> >>>>>>> $> unzip -l
> >>>>>>
> >>>>
> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
> >>>>>>>
> >>>>>>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
> >>>>>>>
> >>>>>>> Our current document structure is
> >>>>>>>
> >>>>>>> docs/
> >>>>>>> ├── docbook
> >>>>>>> │ ├── manual
> >>>>>>> │ │ ├── appendices.html
> >>>>>>> │ │ ├── ch13s02.html
> >>>>>>> │ │ ├── ch13s03.html
> >>>>>>> │ │ ├── ch13s04.html
> >>>>>>> │ │ ├── ch29s04.html
> >>>>>>> │ │ ├── css
> >>>>>>> │ │ │ └── docbook.css
> >>>>>>> │ ├── manual.html
> >>>>>>> │ └── manual.pdf
> >>>>>>> ├── javadoc
> >>>>>>> └── schema
> >>>>>>>
> >>>>>>> My question is:
> >>>>>>>
> >>>>>>> Currently the manual.html (full single-page html) cannot find the
> >>>>>> docbook.css as it is in manual/css/docbook.css.
> >>>>>>>
> >>>>>>> Should be move the manual.html into the manual subfolder?
> >>>>>>> Or should we copy over the css folder for it?
> >>>>>>>
> >>>>>>> LieGrue,
> >>>>>>> strub
> >>>>>>
> >>>>
> >>>>
> >>
> >
>
>
Re: docu cleanup
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
Might be as simple as that it doesn’t work with the installed Java or Maven version on buildbot?
LieGrue,
strub
> Am 15.06.2016 um 22:37 schrieb Mark Struberg <st...@yahoo.de>:
>
> That doesn’t look good…
>
> https://ci.apache.org/builders/openjpa-2.2.x-docs
>
>
>
>> Am 15.06.2016 um 22:35 schrieb Mark Struberg <st...@yahoo.de>:
>>
>>
>> Let’s start with the most obvious.
>>
>> I went through all the ‚HTML manual links on http://openjpa.apache.org/documentation.html
>>
>> Only a few of them are broken
>> * OpenJPA 1.0.5-SNAPSHOT (rest of 1.0.x works fine)
>> * OpenJPA 1.2.4-SNAPSHOT (rest of 1.2.x works fine)
>> * OpenJPA 1.3.0-SNAPSHOT (weird, there are no docs for the 1.3.0 release? Should we remove it at all?)
>>
>> Basically all snapshot links are dead :(
>>
>> I _assume_ they should be hosted here: https://ci.apache.org/projects/openjpa/
>> But only the trunk part is properly filled.
>> I remember that the whole buildbot stuff was broken for at least 1 year++ and I fixed trunk when I did the 2.4.1 release.
>> We need to investigate what’s wrong with the other jobs.
>>
>> LieGrue,
>> strub
>>
>>
>>
>>> Am 15.06.2016 um 17:30 schrieb Jody Grassel <fy...@gmail.com>:
>>>
>>> Pretty much all of the releases other than 2.4.x and trunk. Looking at
>>> http://openjpa.apache.org/documentation.html I see 2.3.x-SNAPSHOT,
>>> 2.2.x-SNAPSHOT, 2.1.x-SNAPSHOT, 2.0.x-SNAPSHOT, 1.3.x-SNAPSHOT,
>>> 1.2.x-SNAPSHOT, and 1.0.x-SNAPSHOT as having broken links. Looking at the
>>> builder for 2.2.x (
>>> https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/317/steps/compile/logs/stdio
>>> ) and the errors in them, I suspect a few changes that went into
>>> trunk./2.4.x need to be back ported to those branches. I was experimenting
>>> locally, looking at what changes had gone into trunk, but haven't cracked
>>> the problem yet.
>>>
>>> On Wed, Jun 15, 2016 at 5:13 AM, Mark Struberg <st...@yahoo.de.invalid>
>>> wrote:
>>>
>>>> Can you point me to the docs which are still broken?
>>>> Might be as easy as a sed replace probably.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
>>>>>
>>>>> What were the steps involved in fixing the 2.4.x docs, so we can restore
>>>>> documentation for earlier versions?
>>>>>
>>>>> On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <
>>>> rmannibucau@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> If we can't change the css path for manual.html I would copy the css
>>>>>> instead of copying manual.html to keep the structure hierarchic.
>>>>>>
>>>>>> Romain Manni-Bucau
>>>>>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>>>>>>
>>>>>>
>>>>>> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
>>>>>>> Hiho!
>>>>>>>
>>>>>>> It took me almost the whole the last week, but now the openjpa doc of
>>>>>> trunk is available again (think it was broken for over a year now).
>>>>>>>
>>>>>>> http://openjpa.staging.apache.org/documentation.html
>>>>>>>
>>>>>>> There is only a minor problem left now:
>>>>>>> the structure of the single-html doesn’t correctly point to the css.
>>>>>>>
>>>>>>> To reproduce what I mean simply run
>>>>>>>
>>>>>>> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
>>>>>>>
>>>>>>> Then look at zip
>>>>>>> $> unzip -l
>>>>>>
>>>> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
>>>>>>>
>>>>>>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
>>>>>>>
>>>>>>> Our current document structure is
>>>>>>>
>>>>>>> docs/
>>>>>>> ├── docbook
>>>>>>> │ ├── manual
>>>>>>> │ │ ├── appendices.html
>>>>>>> │ │ ├── ch13s02.html
>>>>>>> │ │ ├── ch13s03.html
>>>>>>> │ │ ├── ch13s04.html
>>>>>>> │ │ ├── ch29s04.html
>>>>>>> │ │ ├── css
>>>>>>> │ │ │ └── docbook.css
>>>>>>> │ ├── manual.html
>>>>>>> │ └── manual.pdf
>>>>>>> ├── javadoc
>>>>>>> └── schema
>>>>>>>
>>>>>>> My question is:
>>>>>>>
>>>>>>> Currently the manual.html (full single-page html) cannot find the
>>>>>> docbook.css as it is in manual/css/docbook.css.
>>>>>>>
>>>>>>> Should be move the manual.html into the manual subfolder?
>>>>>>> Or should we copy over the css folder for it?
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>
>>>>
>>>>
>>
>
Re: docu cleanup
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
That doesn’t look good…
https://ci.apache.org/builders/openjpa-2.2.x-docs
> Am 15.06.2016 um 22:35 schrieb Mark Struberg <st...@yahoo.de>:
>
>
> Let’s start with the most obvious.
>
> I went through all the ‚HTML manual links on http://openjpa.apache.org/documentation.html
>
> Only a few of them are broken
> * OpenJPA 1.0.5-SNAPSHOT (rest of 1.0.x works fine)
> * OpenJPA 1.2.4-SNAPSHOT (rest of 1.2.x works fine)
> * OpenJPA 1.3.0-SNAPSHOT (weird, there are no docs for the 1.3.0 release? Should we remove it at all?)
>
> Basically all snapshot links are dead :(
>
> I _assume_ they should be hosted here: https://ci.apache.org/projects/openjpa/
> But only the trunk part is properly filled.
> I remember that the whole buildbot stuff was broken for at least 1 year++ and I fixed trunk when I did the 2.4.1 release.
> We need to investigate what’s wrong with the other jobs.
>
> LieGrue,
> strub
>
>
>
>> Am 15.06.2016 um 17:30 schrieb Jody Grassel <fy...@gmail.com>:
>>
>> Pretty much all of the releases other than 2.4.x and trunk. Looking at
>> http://openjpa.apache.org/documentation.html I see 2.3.x-SNAPSHOT,
>> 2.2.x-SNAPSHOT, 2.1.x-SNAPSHOT, 2.0.x-SNAPSHOT, 1.3.x-SNAPSHOT,
>> 1.2.x-SNAPSHOT, and 1.0.x-SNAPSHOT as having broken links. Looking at the
>> builder for 2.2.x (
>> https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/317/steps/compile/logs/stdio
>> ) and the errors in them, I suspect a few changes that went into
>> trunk./2.4.x need to be back ported to those branches. I was experimenting
>> locally, looking at what changes had gone into trunk, but haven't cracked
>> the problem yet.
>>
>> On Wed, Jun 15, 2016 at 5:13 AM, Mark Struberg <st...@yahoo.de.invalid>
>> wrote:
>>
>>> Can you point me to the docs which are still broken?
>>> Might be as easy as a sed replace probably.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>> Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
>>>>
>>>> What were the steps involved in fixing the 2.4.x docs, so we can restore
>>>> documentation for earlier versions?
>>>>
>>>> On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <
>>> rmannibucau@gmail.com>
>>>> wrote:
>>>>
>>>>> If we can't change the css path for manual.html I would copy the css
>>>>> instead of copying manual.html to keep the structure hierarchic.
>>>>>
>>>>> Romain Manni-Bucau
>>>>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>>>>>
>>>>>
>>>>> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
>>>>>> Hiho!
>>>>>>
>>>>>> It took me almost the whole the last week, but now the openjpa doc of
>>>>> trunk is available again (think it was broken for over a year now).
>>>>>>
>>>>>> http://openjpa.staging.apache.org/documentation.html
>>>>>>
>>>>>> There is only a minor problem left now:
>>>>>> the structure of the single-html doesn’t correctly point to the css.
>>>>>>
>>>>>> To reproduce what I mean simply run
>>>>>>
>>>>>> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
>>>>>>
>>>>>> Then look at zip
>>>>>> $> unzip -l
>>>>>
>>> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
>>>>>>
>>>>>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
>>>>>>
>>>>>> Our current document structure is
>>>>>>
>>>>>> docs/
>>>>>> ├── docbook
>>>>>> │ ├── manual
>>>>>> │ │ ├── appendices.html
>>>>>> │ │ ├── ch13s02.html
>>>>>> │ │ ├── ch13s03.html
>>>>>> │ │ ├── ch13s04.html
>>>>>> │ │ ├── ch29s04.html
>>>>>> │ │ ├── css
>>>>>> │ │ │ └── docbook.css
>>>>>> │ ├── manual.html
>>>>>> │ └── manual.pdf
>>>>>> ├── javadoc
>>>>>> └── schema
>>>>>>
>>>>>> My question is:
>>>>>>
>>>>>> Currently the manual.html (full single-page html) cannot find the
>>>>> docbook.css as it is in manual/css/docbook.css.
>>>>>>
>>>>>> Should be move the manual.html into the manual subfolder?
>>>>>> Or should we copy over the css folder for it?
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>
>>>
>>>
>
Re: docu cleanup
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
Let’s start with the most obvious.
I went through all the ‚HTML manual links on http://openjpa.apache.org/documentation.html
Only a few of them are broken
* OpenJPA 1.0.5-SNAPSHOT (rest of 1.0.x works fine)
* OpenJPA 1.2.4-SNAPSHOT (rest of 1.2.x works fine)
* OpenJPA 1.3.0-SNAPSHOT (weird, there are no docs for the 1.3.0 release? Should we remove it at all?)
Basically all snapshot links are dead :(
I _assume_ they should be hosted here: https://ci.apache.org/projects/openjpa/
But only the trunk part is properly filled.
I remember that the whole buildbot stuff was broken for at least 1 year++ and I fixed trunk when I did the 2.4.1 release.
We need to investigate what’s wrong with the other jobs.
LieGrue,
strub
> Am 15.06.2016 um 17:30 schrieb Jody Grassel <fy...@gmail.com>:
>
> Pretty much all of the releases other than 2.4.x and trunk. Looking at
> http://openjpa.apache.org/documentation.html I see 2.3.x-SNAPSHOT,
> 2.2.x-SNAPSHOT, 2.1.x-SNAPSHOT, 2.0.x-SNAPSHOT, 1.3.x-SNAPSHOT,
> 1.2.x-SNAPSHOT, and 1.0.x-SNAPSHOT as having broken links. Looking at the
> builder for 2.2.x (
> https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/317/steps/compile/logs/stdio
> ) and the errors in them, I suspect a few changes that went into
> trunk./2.4.x need to be back ported to those branches. I was experimenting
> locally, looking at what changes had gone into trunk, but haven't cracked
> the problem yet.
>
> On Wed, Jun 15, 2016 at 5:13 AM, Mark Struberg <st...@yahoo.de.invalid>
> wrote:
>
>> Can you point me to the docs which are still broken?
>> Might be as easy as a sed replace probably.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
>>>
>>> What were the steps involved in fixing the 2.4.x docs, so we can restore
>>> documentation for earlier versions?
>>>
>>> On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>>> wrote:
>>>
>>>> If we can't change the css path for manual.html I would copy the css
>>>> instead of copying manual.html to keep the structure hierarchic.
>>>>
>>>> Romain Manni-Bucau
>>>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>>>>
>>>>
>>>> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
>>>>> Hiho!
>>>>>
>>>>> It took me almost the whole the last week, but now the openjpa doc of
>>>> trunk is available again (think it was broken for over a year now).
>>>>>
>>>>> http://openjpa.staging.apache.org/documentation.html
>>>>>
>>>>> There is only a minor problem left now:
>>>>> the structure of the single-html doesn’t correctly point to the css.
>>>>>
>>>>> To reproduce what I mean simply run
>>>>>
>>>>> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
>>>>>
>>>>> Then look at zip
>>>>> $> unzip -l
>>>>
>> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
>>>>>
>>>>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
>>>>>
>>>>> Our current document structure is
>>>>>
>>>>> docs/
>>>>> ├── docbook
>>>>> │ ├── manual
>>>>> │ │ ├── appendices.html
>>>>> │ │ ├── ch13s02.html
>>>>> │ │ ├── ch13s03.html
>>>>> │ │ ├── ch13s04.html
>>>>> │ │ ├── ch29s04.html
>>>>> │ │ ├── css
>>>>> │ │ │ └── docbook.css
>>>>> │ ├── manual.html
>>>>> │ └── manual.pdf
>>>>> ├── javadoc
>>>>> └── schema
>>>>>
>>>>> My question is:
>>>>>
>>>>> Currently the manual.html (full single-page html) cannot find the
>>>> docbook.css as it is in manual/css/docbook.css.
>>>>>
>>>>> Should be move the manual.html into the manual subfolder?
>>>>> Or should we copy over the css folder for it?
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>
>>
>>
Re: docu cleanup
Posted by Jody Grassel <fy...@gmail.com>.
Pretty much all of the releases other than 2.4.x and trunk. Looking at
http://openjpa.apache.org/documentation.html I see 2.3.x-SNAPSHOT,
2.2.x-SNAPSHOT, 2.1.x-SNAPSHOT, 2.0.x-SNAPSHOT, 1.3.x-SNAPSHOT,
1.2.x-SNAPSHOT, and 1.0.x-SNAPSHOT as having broken links. Looking at the
builder for 2.2.x (
https://ci.apache.org/builders/openjpa-2.2.x-docs/builds/317/steps/compile/logs/stdio
) and the errors in them, I suspect a few changes that went into
trunk./2.4.x need to be back ported to those branches. I was experimenting
locally, looking at what changes had gone into trunk, but haven't cracked
the problem yet.
On Wed, Jun 15, 2016 at 5:13 AM, Mark Struberg <st...@yahoo.de.invalid>
wrote:
> Can you point me to the docs which are still broken?
> Might be as easy as a sed replace probably.
>
> LieGrue,
> strub
>
>
> > Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
> >
> > What were the steps involved in fixing the 2.4.x docs, so we can restore
> > documentation for earlier versions?
> >
> > On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > wrote:
> >
> >> If we can't change the css path for manual.html I would copy the css
> >> instead of copying manual.html to keep the structure hierarchic.
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
> >>
> >>
> >> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> >>> Hiho!
> >>>
> >>> It took me almost the whole the last week, but now the openjpa doc of
> >> trunk is available again (think it was broken for over a year now).
> >>>
> >>> http://openjpa.staging.apache.org/documentation.html
> >>>
> >>> There is only a minor problem left now:
> >>> the structure of the single-html doesn’t correctly point to the css.
> >>>
> >>> To reproduce what I mean simply run
> >>>
> >>> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
> >>>
> >>> Then look at zip
> >>> $> unzip -l
> >>
> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
> >>>
> >>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
> >>>
> >>> Our current document structure is
> >>>
> >>> docs/
> >>> ├── docbook
> >>> │ ├── manual
> >>> │ │ ├── appendices.html
> >>> │ │ ├── ch13s02.html
> >>> │ │ ├── ch13s03.html
> >>> │ │ ├── ch13s04.html
> >>> │ │ ├── ch29s04.html
> >>> │ │ ├── css
> >>> │ │ │ └── docbook.css
> >>> │ ├── manual.html
> >>> │ └── manual.pdf
> >>> ├── javadoc
> >>> └── schema
> >>>
> >>> My question is:
> >>>
> >>> Currently the manual.html (full single-page html) cannot find the
> >> docbook.css as it is in manual/css/docbook.css.
> >>>
> >>> Should be move the manual.html into the manual subfolder?
> >>> Or should we copy over the css folder for it?
> >>>
> >>> LieGrue,
> >>> strub
> >>
>
>
Re: docu cleanup
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
Can you point me to the docs which are still broken?
Might be as easy as a sed replace probably.
LieGrue,
strub
> Am 14.06.2016 um 20:35 schrieb Jody Grassel <fy...@gmail.com>:
>
> What were the steps involved in fixing the 2.4.x docs, so we can restore
> documentation for earlier versions?
>
> On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> If we can't change the css path for manual.html I would copy the css
>> instead of copying manual.html to keep the structure hierarchic.
>>
>> Romain Manni-Bucau
>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>>
>>
>> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
>>> Hiho!
>>>
>>> It took me almost the whole the last week, but now the openjpa doc of
>> trunk is available again (think it was broken for over a year now).
>>>
>>> http://openjpa.staging.apache.org/documentation.html
>>>
>>> There is only a minor problem left now:
>>> the structure of the single-html doesn’t correctly point to the css.
>>>
>>> To reproduce what I mean simply run
>>>
>>> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
>>>
>>> Then look at zip
>>> $> unzip -l
>> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
>>>
>>> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
>>>
>>> Our current document structure is
>>>
>>> docs/
>>> ├── docbook
>>> │ ├── manual
>>> │ │ ├── appendices.html
>>> │ │ ├── ch13s02.html
>>> │ │ ├── ch13s03.html
>>> │ │ ├── ch13s04.html
>>> │ │ ├── ch29s04.html
>>> │ │ ├── css
>>> │ │ │ └── docbook.css
>>> │ ├── manual.html
>>> │ └── manual.pdf
>>> ├── javadoc
>>> └── schema
>>>
>>> My question is:
>>>
>>> Currently the manual.html (full single-page html) cannot find the
>> docbook.css as it is in manual/css/docbook.css.
>>>
>>> Should be move the manual.html into the manual subfolder?
>>> Or should we copy over the css folder for it?
>>>
>>> LieGrue,
>>> strub
>>
Re: docu cleanup
Posted by Jody Grassel <fy...@gmail.com>.
What were the steps involved in fixing the 2.4.x docs, so we can restore
documentation for earlier versions?
On Mon, Mar 21, 2016 at 7:04 AM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> If we can't change the css path for manual.html I would copy the css
> instead of copying manual.html to keep the structure hierarchic.
>
> Romain Manni-Bucau
> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>
>
> 2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> > Hiho!
> >
> > It took me almost the whole the last week, but now the openjpa doc of
> trunk is available again (think it was broken for over a year now).
> >
> > http://openjpa.staging.apache.org/documentation.html
> >
> > There is only a minor problem left now:
> > the structure of the single-html doesn’t correctly point to the css.
> >
> > To reproduce what I mean simply run
> >
> > $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
> >
> > Then look at zip
> > $> unzip -l
> ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
> >
> > This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
> >
> > Our current document structure is
> >
> > docs/
> > ├── docbook
> > │ ├── manual
> > │ │ ├── appendices.html
> > │ │ ├── ch13s02.html
> > │ │ ├── ch13s03.html
> > │ │ ├── ch13s04.html
> > │ │ ├── ch29s04.html
> > │ │ ├── css
> > │ │ │ └── docbook.css
> > │ ├── manual.html
> > │ └── manual.pdf
> > ├── javadoc
> > └── schema
> >
> > My question is:
> >
> > Currently the manual.html (full single-page html) cannot find the
> docbook.css as it is in manual/css/docbook.css.
> >
> > Should be move the manual.html into the manual subfolder?
> > Or should we copy over the css folder for it?
> >
> > LieGrue,
> > strub
>
Re: docu cleanup
Posted by Romain Manni-Bucau <rm...@gmail.com>.
If we can't change the css path for manual.html I would copy the css
instead of copying manual.html to keep the structure hierarchic.
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
2016-03-21 13:00 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> Hiho!
>
> It took me almost the whole the last week, but now the openjpa doc of trunk is available again (think it was broken for over a year now).
>
> http://openjpa.staging.apache.org/documentation.html
>
> There is only a minor problem left now:
> the structure of the single-html doesn’t correctly point to the css.
>
> To reproduce what I mean simply run
>
> $> mvn clean site install -DskipTests -Pjavadoc-profile,docbook-profile
>
> Then look at zip
> $> unzip -l ./openjpa-project/target/site/downloads/apache-openjpa-2.4.2-SNAPSHOT-binary.zip
>
> This contains a folder apache-openjpa-2.4.2-SNAPSHOT/docs/
>
> Our current document structure is
>
> docs/
> ├── docbook
> │ ├── manual
> │ │ ├── appendices.html
> │ │ ├── ch13s02.html
> │ │ ├── ch13s03.html
> │ │ ├── ch13s04.html
> │ │ ├── ch29s04.html
> │ │ ├── css
> │ │ │ └── docbook.css
> │ ├── manual.html
> │ └── manual.pdf
> ├── javadoc
> └── schema
>
> My question is:
>
> Currently the manual.html (full single-page html) cannot find the docbook.css as it is in manual/css/docbook.css.
>
> Should be move the manual.html into the manual subfolder?
> Or should we copy over the css folder for it?
>
> LieGrue,
> strub