In the midst of the reorganization, the targets that would build the
website content were separated from the content. The usual approach was
to build the documentation application and then upload that, so those
Ant targets marched over to the Apps subproject. Meanwhile, the content
is still under Core (in docs). I usually just built the website locally
(there was a target for that) and would then scp the pages up to the
server, without messing about with the WAR.
Yes, this is what I have done in the past. So what you are saying is that currently, the website build is broken. What I'm wanting to do is update the website so I can announce Struts Flow. Struts Flow will add three new pages so that might be too big to just hack the HTML itself.
The end-game is to create a separate "site" subproject for the
top-level project that would introduce the project as a whole and link
into each subproject. Each subproject would have its own set of
documentation, in its own folder, perhaps done through Maven. Other
"mega-projects", like Logging, seem to be doing that now. Building the
Struts site would then be something like building the Jakarta Commons site.
Well, that gets us back into the Maven vs. Ant debate. I'd imagine we don't want to have part of the build require Ant, and the other require Maven. Are there any examples of this being done that use Ant?
Don
-Ted.
On Tue, 15 Feb 2005 17:55:53 -0800, Don Brown wrote:
Ok, I give up - how do you build the Struts website? Last I remember, I used ant which pulled the content from /docs but I can't seem to find any site building task in build.xml. Are we now only using maven and /xdocs?
Don
-------------------------------------------------------------------- - 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
