On 8/11/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> From: "Wendy Smoak" <[EMAIL PROTECTED]>
> > One remaining concern about the website conversion:  If I copy the files
> > into build/xdocs, what happens when someone checks out struts/current and
> > gets the 'build' directory within every subproject?  I have a feeling it's
> > going to retrieve all that documentation a dozen times, once for each
> > subproject, but maybe Subversion clients are smarter than that.
> > Otherwise, can subversion be configured to exclude the 'xdocs' directory?
> 
> (I'm really not talking to myself-- James IM'd right after I posted the
> message above to confirm that this is a legitimate issue.)
> 
> When I asked a question recently on maven-user, they suggested having a
> separate sub-project for the website.  That didn't initially work for me
> because if you run 'maven multiproject:site' from /struts/current/build, it
> sees the 'website' directory as just another sub-project and puts the
> documentation under struts.apache.org/website-- breaking every link into the
> Struts site.
> 
> However, having a separate sub-project for the website and building the site
> _from there_ works.  I now have struts/current/site containing the 'xdocs'
> directory with all of the xml (and other) files from the existing site, and
> executing 'maven multiproject:site' from struts/current/site does the right
> thing.
> 
> Having a separate sub-project for the site also helps with the goal of
> clearly separating the website from the project documentation.
> 
> Are there any objections to having 'site' or 'website' as a new sub-project?

None at all. As Ted mentioned, that was the original plan. :-)

--
Martin Cooper


> Thanks,
> Wendy
> 
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to