On Wed, 16 Feb 2005 14:17:24 -0500, Ted Husted <[EMAIL PROTECTED]> wrote:
> On Wed, 16 Feb 2005 10:42:36 -0800, Don Brown wrote:
> > I know I haven't been keeping up on this as I should have, but
> > wasn't Martin reworking all the Ant scripts?  Perhaps website
> > building was included?
> >
> > Don
> 
> Not that I can see. The HTML pages are built using stylesheets, and the only 
> place the Core build file does that is to create the TLDs.
> 

Yah, I never got that far.

> The Core jars seem to build just fine (<yeah!/>), including the release 
> target.

Building core with Maven should be just fine as well.

> The website was associated with building the documentation.war, but that's a 
> separate subproject from Core now. Apps doesn't even have a master build.xml 
> yet.
> 
> For now, I'd suggest moving the XML documents associated with the 1.2 website 
> to a separate Site subproject. We can get that to build (or "transform") into 
> HTML easily enough by cannibalizing the 1.2 build files. We wouldn't have to 
> worry about a WAR for this. Once we have the transformed pages, we can just 
> scp them up.
> 

My thinking was that we'd have 'site' + all subprojects, where 'core'
would  play in the same way as other subprojects. Since that will
involve separating 'site' files from 'core' files, I'd prefer, in the
interim, to build the site from where it is now, rather than move
everything out and then move some of it back again later. If we have a
separate build file that reaches over into other subprojects, I think
that's OK as a stopgap measure.

> For new projects, ideally we'd want Site to link to the subproject for 
> detail, rather than try to plug everything into Site. (I suppose.) The 
> subproject links should probably be absolute links to 
> struts.apache.org/$subproject, so that we don't have to build it all locally.
> 

+1

--
Martin Cooper


> Maven Jumpstart
> 
> My main station is in the shop, and I'm having trouble committing from the 
> laptop for some reason. But, if anyone is interested, I have a 
> build.properties file for Core that uses the Maven for a jumpstart. You can 
> use the Maven build to acquire the JARs, and this version of the properties 
> file will then get them out of your Maven repository.
> 
> -Ted.
> 
> 
> ---------------------------------------------------------------------
> 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