10:17 a.m.
Per https://issues.jboss.org/browse/TEIID-1875 I am moving the docs to
confluence, so hold off your commits to documents until further notice.
I will let you know as soon as I am done.
Note that this is only applies for the Teiid 8.0 version.
Ramesh..
9:18 p.m.
Steve,
Please take look at https://docs.jboss.org/author/display/TEIID/Home for
new documents home. Make sure everything looks OK. I think the javacc
file did not quite came out right, we may need to fix this.
If we think this looks good and I go ahead clean-up the svn repository
and remove document projects.
Thanks
Ramesh..
On Tue, 2012-01-17 at 10:17 -0600, Ramesh Reddy wrote:
Per https://issues.jboss.org/browse/TEIID-1875 I am moving the docs
to
confluence, so hold off your commits to documents until further notice.
I will let you know as soon as I am done.
Note that this is only applies for the Teiid 8.0 version.
Ramesh..
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
10:16 a.m.
Yes, anything with nested or complex tables didn't import very well. Also the xml
examples sometimes have errors rather than showing the docs.
For the grammar we have control over what docbook is generated, so I will take a look at
simplifying the structure and re-import. Ideally we would use a process built into the
release to update confluence.
Maybe we should just lock the documentation module for now rather than deleting so that it
will be easier to access the source until the docs are corrected. Will we still even need
separate downloadable pdf docs, or will we just want to put the pdfs in the kits?
Steve
----- Original Message -----
Steve,
Please take look at https://docs.jboss.org/author/display/TEIID/Home
for
new documents home. Make sure everything looks OK. I think the javacc
file did not quite came out right, we may need to fix this.
If we think this looks good and I go ahead clean-up the svn
repository
and remove document projects.
Thanks
Ramesh..
On Tue, 2012-01-17 at 10:17 -0600, Ramesh Reddy wrote:
> Per https://issues.jboss.org/browse/TEIID-1875 I am moving the docs
> to
> confluence, so hold off your commits to documents until further
> notice.
> I will let you know as soon as I am done.
>
> Note that this is only applies for the Teiid 8.0 version.
>
> Ramesh..
>
> _______________________________________________
> teiid-dev mailing list
> teiid-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-dev
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
10:42 a.m.
On Wed, 2012-01-18 at 11:16 -0500, Steven Hawkins wrote:
Yes, anything with nested or complex tables didn't import very
well. Also the xml examples sometimes have errors rather than showing the docs.
I
will see if I can correct some of these then.
For the grammar we have control over what docbook is generated, so I will take a look at
simplifying the structure and re-import. Ideally we would use a process built into the
release to update confluence.
Sounds good, only issue I have seen is there seems
to be no import of
HTML. They support richtext or markup. We need to some how generate that
markup.
Maybe we should just lock the documentation module for now rather than deleting so that
it will be easier to access the source until the docs are corrected. Will we still even
need separate downloadable pdf docs, or will we just want to put the pdfs in the kits?
OK, I do not think we need separate PDF downloads anymore, as any user
can export these docs into PDF if they want. Yes, we need to change the
release process such that at the time of release we make a copy of the
sub-space and assign the release number. As per adding the PDF to docs,
I have not seen Jboss AS doing the same, so I am OK if we do not include
them anymore for ease of doing the build in one step.
Ramesh..
10:52 a.m.
----- Original Message -----
On Wed, 2012-01-18 at 11:16 -0500, Steven Hawkins wrote:
> Yes, anything with nested or complex tables didn't import very
> well. Also the xml examples sometimes have errors rather than
> showing the docs.
I will see if I can correct some of these then.
>
> For the grammar we have control over what docbook is generated, so
> I will take a look at simplifying the structure and re-import.
> Ideally we would use a process built into the release to update
> confluence.
Sounds good, only issue I have seen is there seems to be no import of
HTML. They support richtext or markup. We need to some how generate
that
markup.
>
> Maybe we should just lock the documentation module for now rather
> than deleting so that it will be easier to access the source until
> the docs are corrected. Will we still even need separate
> downloadable pdf docs, or will we just want to put the pdfs in the
> kits?
OK, I do not think we need separate PDF downloads anymore, as any
user
can export these docs into PDF if they want. Yes, we need to change
the
release process such that at the time of release we make a copy of
the
sub-space and assign the release number. As per adding the PDF to
docs,
I have not seen Jboss AS doing the same, so I am OK if we do not
include
them anymore for ease of doing the build in one step.
If we don't add the pdfs, then we'll need to kick that task over to
productization. In the past we've been required to include the docs with the kits for
environments that are not allowed to have internet connectivity.
Ramesh..
1:44 p.m.
The documents are now migrated to
https://docs.jboss.org/author/display/TEIIDDoc/Home
Please make any future modifications to the documents there.
Thanks.
Ramesh..
On Wed, 2012-01-18 at 11:52 -0500, Steven Hawkins wrote:
----- Original Message -----
> On Wed, 2012-01-18 at 11:16 -0500, Steven Hawkins wrote:
> > Yes, anything with nested or complex tables didn't import very
> > well. Also the xml examples sometimes have errors rather than
> > showing the docs.
> I will see if I can correct some of these then.
> >
> > For the grammar we have control over what docbook is generated, so
> > I will take a look at simplifying the structure and re-import.
> > Ideally we would use a process built into the release to update
> > confluence.
> Sounds good, only issue I have seen is there seems to be no import of
> HTML. They support richtext or markup. We need to some how generate
> that
> markup.
> >
> > Maybe we should just lock the documentation module for now rather
> > than deleting so that it will be easier to access the source until
> > the docs are corrected. Will we still even need separate
> > downloadable pdf docs, or will we just want to put the pdfs in the
> > kits?
> OK, I do not think we need separate PDF downloads anymore, as any
> user
> can export these docs into PDF if they want. Yes, we need to change
> the
> release process such that at the time of release we make a copy of
> the
> sub-space and assign the release number. As per adding the PDF to
> docs,
> I have not seen Jboss AS doing the same, so I am OK if we do not
> include
> them anymore for ease of doing the build in one step.
If we don't add the pdfs, then we'll need to kick that task over to
productization. In the past we've been required to include the docs with the kits for
environments that are not allowed to have internet connectivity.
>
> Ramesh..
>
>
>
4710
days inactive
4713
days old
5 comments
2 participants
participants (2)
-
Ramesh Reddy -
Steven Hawkins