Re: documentation problems

I opened WW-1701 for this. * https://issues.apache.org/struts/browse/WW-1701 I should note that anyone with karma to the docs could handle this one. It doesn't need to be a committer. -Ted. On 1/16/07, Don Brown <[EMAIL PROTECTED]> wrote: I guess that would work too. The big thing is they st

Re: documentation problems

I guess that would work too. The big thing is they stay listed in the registry and use a similar documentation layout, but it wouldn't hurt to move the bulk of the content to the other space. Don Ted Husted wrote: On 1/16/07, Don Brown <[EMAIL PROTECTED]> wrote: Well, my concern then is tha

Re: documentation problems

On 1/16/07, Don Brown <[EMAIL PROTECTED]> wrote: Well, my concern then is that we wouldn't include any plugin documentation with our release. While this is fine for third-party plugins, it is important we provide docs on key plugins like the Spring plugin. Then perhaps we should put only a ske

Re: documentation problems

Right, normally you would use an inter-space Confluence link like [S2PLUGINS:Home], but the auto-export to html will render those links invalid. Therefore, you have to hard-code a full URL to the exported version like below. Don Ted Husted wrote: * http://cwiki.apache.org/S2PLUGINS/home.htm

Re: documentation problems

Well, my concern then is that we wouldn't include any plugin documentation with our release. While this is fine for third-party plugins, it is important we provide docs on key plugins like the Spring plugin. Don Ted Husted wrote: I don't believe that we want to include a snapshot of the Plu

Re: documentation problems

I don't believe that we want to include a snapshot of the Plugin Registry in the distribution, so there would not seem to be a need to synch it to struts.apache.org. It is setup to autoexport, and we can link to the copy on cwiki (which should be updated on a per-change basis). -Ted. On 1/2/07,

Re: documentation problems

* http://cwiki.apache.org/S2PLUGINS/home.html On 1/16/07, Musachy Barroso <[EMAIL PROTECTED]> wrote: How should I link to the plugins page? is there a prefix? musachy Don Brown wrote: > Thanks for pointing these out, but please feel free to take the next > step and correct them. By editing th

Re: documentation problems

How should I link to the plugins page? is there a prefix? musachy Don Brown wrote: Thanks for pointing these out, but please feel free to take the next step and correct them. By editing the original Confluence pages, found at http://cwiki.apache.org/confluence/display/WW, these snippet error

Re: documentation problems

The main docs take a little while to sync and no, I don't believe the plugin registry has been setup to sync yet. Don Musachy Barroso wrote: I fixed the snippets. The broken links are fine on Confluence, but broken on main doc, is the plugin registry available on the main doc already? musac

Re: documentation problems

I fixed the snippets. The broken links are fine on Confluence, but broken on main doc, is the plugin registry available on the main doc already? musachy Musachy Barroso wrote: Macro snippet errors: http://struts.apache.org/2.x/docs/validation.html http://struts.apache.org/2.x/docs/type-conver

Re: documentation problems

After re-reading your email, "By editing the original Confluence pages", got it :) musachy Musachy Barroso wrote: I would, I just don't have rights :) musachy Don Brown wrote: Thanks for pointing these out, but please feel free to take the next step and correct them. By editing the original

Re: documentation problems

I would, I just don't have rights :) musachy Don Brown wrote: Thanks for pointing these out, but please feel free to take the next step and correct them. By editing the original Confluence pages, found at http://cwiki.apache.org/confluence/display/WW, these snippet errors can be corrected.

Re: documentation problems

Thanks for pointing these out, but please feel free to take the next step and correct them. By editing the original Confluence pages, found at http://cwiki.apache.org/confluence/display/WW, these snippet errors can be corrected. The reason so many are broken is that the pages were pointing to

documentation problems

Macro snippet errors: http://struts.apache.org/2.x/docs/validation.html http://struts.apache.org/2.x/docs/type-conversion.html http://struts.apache.org/2.x/docs/localization.html http://struts.apache.org/2.x/docs/action-chaining.html http://struts.apache.org/2.x/docs/interceptors.html http://strut