Like this:

 * http://cwiki.apache.org/S2PLUGINS/rest-plugin.html

-T.

On Jan 9, 2008 8:44 AM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> Ok, I'll just move it there then, and create a link (I'm not sure if
> that's what you meant by a "bridge page"?) in the S2PLUGINS space to
> it.
>
> Thanks.
>
> Nils-H
>
>
> On Jan 9, 2008 2:39 PM, Ted Husted <[EMAIL PROTECTED]> wrote:
> > If the plugin is bundled with the distribution, then the documentation
> > can go here
> >
> >  * http://struts.apache.org/2.x/docs/plugin-developers-guide.html
> >
> > And then we just put a bridge page in the S2PLUGINS space, so that
> > people can get here from there :)
> >
> > The S2PLUGIN space covers both the plugins that we bundle, and the
> > plugins that other people distribute.
> >
> > If the documentation for a bundled plugin in the S2PLUGINS space, and
> > the authors have a CLA on file, then we could move it to WW.
> >
> > HTH, Ted
> >
> >
> > On Jan 9, 2008 8:34 AM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote:
> > > Where's the correct place to put documentation for S2 plugins? I've
> > > noticed that some reside in the S2PLUGINS space in the wiki, and some
> > > are in the WW space. I put the portlet plugin documentation in the
> > > S2PLUGINS space, which I have a feeling was the wrong place to put
> > > it... It aparently also causes problems when the pages are exported,
> > > since the links point into the wiki, and not the exported static
> > > content.
> > >
> > > Nils-H
> >
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
HTH, Ted
 * <http://www.StrutsMentor.com/>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to