You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by lewis john mcgibbney <le...@apache.org> on 2017/03/28 15:39:27 UTC
OODT Documentation Tied up in Source Code
Hi dev@,
There is a whole host of documentation tied in up various Maven modules.
These used to be deployed to the Website, however this is no longer the
case.
An example is the primary documentation on Workflow Manager [0].
Where should we put this? On the wiki or on the Website?
Lewis
[0] https://github.com/apache/oodt/tree/master/workflow/src/site/xdoc
--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney
Re: OODT Documentation Tied up in Source Code
Posted by lewis john mcgibbney <le...@apache.org>.
Post publication steps are perhaps the best, most logical snippet of
sincere knowledge I've read in a looooong time. It all makes so much sense
now!
On Tue, Mar 28, 2017 at 10:59 AM Chris Mattmann <ma...@apache.org> wrote:
> Check this out:
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61323299
>
>
>
> On 3/28/17, 1:44 PM, "Tom Barber" <to...@meteorite.bi> wrote:
>
> Yeah, there was a plan to keep it getting deployed, but I couldn't
> work out
> how to get the url linkage right as an OODT subsite from the Maven
> build.
>
> Chris pointed me to Sean and thats about as far as it got. But if we
> can
> build a maven site, copying it into the main site is a piece of cake.
>
> Tom
>
> On Tue, Mar 28, 2017 at 5:11 PM, lewis john mcgibbney <
> lewismc@apache.org>
> wrote:
>
> > ACK if we could retain this approach that would be great.
> >
> > On Tue, Mar 28, 2017 at 8:42 AM, Chris Mattmann <mattmann@apache.org
> >
> > wrote:
> >
> > > Lewis, since no one has stepped up to convert it to the Wiki why
> not just
> > > keep it attached to Maven and start publishing it again?
> > >
> > > Sean Kelly wrote a tool to do this – TomB can it be integrated
> into your
> > > new approach?
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > >
> > >
> > > On 3/28/17, 11:39 AM, "lewis john mcgibbney" <le...@apache.org>
> wrote:
> > >
> > > Hi dev@,
> > > There is a whole host of documentation tied in up various Maven
> > > modules.
> > > These used to be deployed to the Website, however this is no
> longer
> > the
> > > case.
> > > An example is the primary documentation on Workflow Manager
> [0].
> > > Where should we put this? On the wiki or on the Website?
> > > Lewis
> > >
> > > [0] https://github.com/apache/oodt/tree/master/workflow/src/
> > site/xdoc
> > >
> > >
> > > --
> > > http://home.apache.org/~lewismc/
> > > @hectorMcSpector
> > > http://www.linkedin.com/in/lmcgibbney
> > >
> > >
> > >
> > >
> >
> >
> > --
> > http://home.apache.org/~lewismc/
> > @hectorMcSpector
> > http://www.linkedin.com/in/lmcgibbney
> >
>
>
>
> --
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney
Re: OODT Documentation Tied up in Source Code
Posted by Chris Mattmann <ma...@apache.org>.
Check this out:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61323299
On 3/28/17, 1:44 PM, "Tom Barber" <to...@meteorite.bi> wrote:
Yeah, there was a plan to keep it getting deployed, but I couldn't work out
how to get the url linkage right as an OODT subsite from the Maven build.
Chris pointed me to Sean and thats about as far as it got. But if we can
build a maven site, copying it into the main site is a piece of cake.
Tom
On Tue, Mar 28, 2017 at 5:11 PM, lewis john mcgibbney <le...@apache.org>
wrote:
> ACK if we could retain this approach that would be great.
>
> On Tue, Mar 28, 2017 at 8:42 AM, Chris Mattmann <ma...@apache.org>
> wrote:
>
> > Lewis, since no one has stepped up to convert it to the Wiki why not just
> > keep it attached to Maven and start publishing it again?
> >
> > Sean Kelly wrote a tool to do this – TomB can it be integrated into your
> > new approach?
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 3/28/17, 11:39 AM, "lewis john mcgibbney" <le...@apache.org> wrote:
> >
> > Hi dev@,
> > There is a whole host of documentation tied in up various Maven
> > modules.
> > These used to be deployed to the Website, however this is no longer
> the
> > case.
> > An example is the primary documentation on Workflow Manager [0].
> > Where should we put this? On the wiki or on the Website?
> > Lewis
> >
> > [0] https://github.com/apache/oodt/tree/master/workflow/src/
> site/xdoc
> >
> >
> > --
> > http://home.apache.org/~lewismc/
> > @hectorMcSpector
> > http://www.linkedin.com/in/lmcgibbney
> >
> >
> >
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>
Re: OODT Documentation Tied up in Source Code
Posted by Tom Barber <to...@meteorite.bi>.
Yeah, there was a plan to keep it getting deployed, but I couldn't work out
how to get the url linkage right as an OODT subsite from the Maven build.
Chris pointed me to Sean and thats about as far as it got. But if we can
build a maven site, copying it into the main site is a piece of cake.
Tom
On Tue, Mar 28, 2017 at 5:11 PM, lewis john mcgibbney <le...@apache.org>
wrote:
> ACK if we could retain this approach that would be great.
>
> On Tue, Mar 28, 2017 at 8:42 AM, Chris Mattmann <ma...@apache.org>
> wrote:
>
> > Lewis, since no one has stepped up to convert it to the Wiki why not just
> > keep it attached to Maven and start publishing it again?
> >
> > Sean Kelly wrote a tool to do this – TomB can it be integrated into your
> > new approach?
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > On 3/28/17, 11:39 AM, "lewis john mcgibbney" <le...@apache.org> wrote:
> >
> > Hi dev@,
> > There is a whole host of documentation tied in up various Maven
> > modules.
> > These used to be deployed to the Website, however this is no longer
> the
> > case.
> > An example is the primary documentation on Workflow Manager [0].
> > Where should we put this? On the wiki or on the Website?
> > Lewis
> >
> > [0] https://github.com/apache/oodt/tree/master/workflow/src/
> site/xdoc
> >
> >
> > --
> > http://home.apache.org/~lewismc/
> > @hectorMcSpector
> > http://www.linkedin.com/in/lmcgibbney
> >
> >
> >
> >
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>
Re: OODT Documentation Tied up in Source Code
Posted by lewis john mcgibbney <le...@apache.org>.
ACK if we could retain this approach that would be great.
On Tue, Mar 28, 2017 at 8:42 AM, Chris Mattmann <ma...@apache.org> wrote:
> Lewis, since no one has stepped up to convert it to the Wiki why not just
> keep it attached to Maven and start publishing it again?
>
> Sean Kelly wrote a tool to do this – TomB can it be integrated into your
> new approach?
>
> Cheers,
> Chris
>
>
>
>
> On 3/28/17, 11:39 AM, "lewis john mcgibbney" <le...@apache.org> wrote:
>
> Hi dev@,
> There is a whole host of documentation tied in up various Maven
> modules.
> These used to be deployed to the Website, however this is no longer the
> case.
> An example is the primary documentation on Workflow Manager [0].
> Where should we put this? On the wiki or on the Website?
> Lewis
>
> [0] https://github.com/apache/oodt/tree/master/workflow/src/site/xdoc
>
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>
>
>
>
--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney
Re: OODT Documentation Tied up in Source Code
Posted by Chris Mattmann <ma...@apache.org>.
Lewis, since no one has stepped up to convert it to the Wiki why not just
keep it attached to Maven and start publishing it again?
Sean Kelly wrote a tool to do this – TomB can it be integrated into your
new approach?
Cheers,
Chris
On 3/28/17, 11:39 AM, "lewis john mcgibbney" <le...@apache.org> wrote:
Hi dev@,
There is a whole host of documentation tied in up various Maven modules.
These used to be deployed to the Website, however this is no longer the
case.
An example is the primary documentation on Workflow Manager [0].
Where should we put this? On the wiki or on the Website?
Lewis
[0] https://github.com/apache/oodt/tree/master/workflow/src/site/xdoc
--
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney