Bug 230312 - List of changes Hibernate has to make to make their docs compatible with docbot at the XML level
Summary: List of changes Hibernate has to make to make their docs compatible with docb...
Alias: None
Product: JBoss Enterprise Application Platform 4
Classification: JBoss
Component: doc-Hibernate_Reference_Guide
Version: 4.2.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Joshua Wulf
QA Contact:
Depends On:
Blocks: 230313
TreeView+ depends on / blocked
Reported: 2007-02-28 08:08 UTC by Michael Yuan
Modified: 2014-10-19 22:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-06-18 12:04:41 UTC
Type: ---

Attachments (Terms of Use)

Description Michael Yuan 2007-02-28 08:08:06 UTC
I understand that the docbot build system has some special requirements w.r.t
how the XML files are structured (the lang parameter and what else?). Can we
have a list of such requirements by comparing the Hibernate docs in the ES repo
with the Hibernate docs in the Hibernate SVN? Thanks.

The Hibernate SVN is this:

Comment 1 Michael Yuan 2007-02-28 08:12:31 UTC
I mean, the goal is to pull docbook XML files from Hibernate SVN, upload them
into the ES CVS, and have the docbot build it successfully. The Hibernate and ES
do not need to share the same build files (actually, Hibernate uses ANT and ES
uses make, AFAIK).

Comment 2 Michael Hideo 2007-03-01 05:35:29 UTC

Confirm we will sync with upstream for this release. Translations will remain
downstream in cvs.devel.

Any writers assigned to this project will move into the hibernate upstream svn
source and make their commits there. To build, they will sync back down via docbot.


I'll hand over the hibernate contact as it has been presented. Can you check
with him and confirm that the svn version in HEAD is 4.2.0  When you have
confirmed, let me know and then we will branch and re-sync.

- Mike

Comment 3 Michael Hideo 2007-06-06 04:50:41 UTC
Adding 'cc ecs-dev-list@redhat.com for team coverage

Note You need to log in before you can comment on or make changes to this bug.