You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Don Brown <mr...@twdata.org> on 2005/02/16 02:55:53 UTC
Building Struts Website
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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Craig McClanahan <cr...@gmail.com>.
Historically, the Struts website has just been a copy of the
struts-documentation.war webapp, uploaded to the server and then
unpacked into "/www/struts.apache.org/". The only semi tricky part is
you have to make sure the permissions are set correctly (set your
umask to 0002 before unpacking, and ensure afterwards that the CGIs
for downloads are still executable).
Craig
On Tue, 15 Feb 2005 17:55:53 -0800, Don Brown <mr...@twdata.org> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Don Brown <mr...@apache.org>.
Thanks, and done. Let me know if there is anything I missed.
Don
Ted Husted wrote:
> Never mind. I ran svnpasswd on the new machine, and now everything works :)
>
> So, Don, you can make the changes, use core/build-site.xml to rebuild the site, and scp it up to /www/struts.apache.org.
>
> -T.
>
> On Thu, 17 Feb 2005 07:20:48 -0500, Ted Husted wrote:
>
>> OK, I'm still having trouble committing from this machine, so I
>> added the stopgap build file through bugzilla.
>>
>> * http://issues.apache.org/bugzilla/show_bug.cgi?id=33617
>>
>> If anyone want's to jump in and help setup the Struts subprojects
>> as Maven builds, I'm sure Martin, James, et al, will appreciate a
>> hand.
>>
>> Essentially, we want to do the same thing that Jakarta Commons is
>> doing.
>>
>> -Ted.
>>
>> On Thu, 17 Feb 2005 06:25:28 -0500, Ted Husted wrote:
>>
>>
>>> On Wed, 16 Feb 2005 16:30:09 -0800, Martin Cooper wrote:
>>>
>>>
>>>> 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.
>>>>
>>>>
>>>
>>> As a stopgap, I'll work up a quick Ant build to create the
>>> website under Core.
>>>
>>> -Ted.
>>>
>>>
>>> ------------------------------------------------------------------
>>> -- - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>> --------------------------------------------------------------------
>> - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
>> additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
Never mind. I ran svnpasswd on the new machine, and now everything works :)
So, Don, you can make the changes, use core/build-site.xml to rebuild the site, and scp it up to /www/struts.apache.org.
-T.
On Thu, 17 Feb 2005 07:20:48 -0500, Ted Husted wrote:
>�OK, I'm still �having trouble committing from this machine, so I
>�added the stopgap build file through bugzilla.
>
>�* http://issues.apache.org/bugzilla/show_bug.cgi?id=33617
>
>�If anyone want's to jump in and help setup the Struts subprojects
>�as Maven builds, I'm sure Martin, James, et al, will appreciate a
>�hand.
>
>�Essentially, we want to do the same thing that Jakarta Commons is
>�doing.
>
>�-Ted.
>
>�On Thu, 17 Feb 2005 06:25:28 -0500, Ted Husted wrote:
>
>>�On Wed, 16 Feb 2005 16:30:09 -0800, Martin Cooper wrote:
>>
>>>�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.
>>>
>>>
>>�As a stopgap, I'll work up a quick Ant build to create the
>>�website �under Core.
>>
>>�-Ted.
>>
>>
>>�------------------------------------------------------------------
>>�-- �- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org �
>>�For additional commands, e-mail: dev-help@struts.apache.org
>
>
>�--------------------------------------------------------------------
>�- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
>�additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
OK, I'm still having trouble committing from this machine, so I added the stopgap build file through bugzilla.
* http://issues.apache.org/bugzilla/show_bug.cgi?id=33617
If anyone want's to jump in and help setup the Struts subprojects as Maven builds, I'm sure Martin, James, et al, will appreciate a hand.
Essentially, we want to do the same thing that Jakarta Commons is doing.
-Ted.
On Thu, 17 Feb 2005 06:25:28 -0500, Ted Husted wrote:
>�On Wed, 16 Feb 2005 16:30:09 -0800, Martin Cooper wrote:
>>�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.
>>
>
>�As a stopgap, I'll work up a quick Ant build to create the website
>�under Core.
>
>�-Ted.
>
>
>�--------------------------------------------------------------------
>�- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>�For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
On Wed, 16 Feb 2005 16:30:09 -0800, Martin Cooper wrote:
>�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.
As a stopgap, I'll work up a quick Ant build to create the website under Core.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Martin Cooper <mf...@gmail.com>.
On Wed, 16 Feb 2005 14:17:24 -0500, Ted Husted <hu...@apache.org> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Martin Cooper <mf...@gmail.com>.
(Man, I am drowning in dev@ messages these days! I'm about 100 behind
right now and losing...)
At one point I did start on an Ant based build system, since I had
just finished one for my day job. However, before I got too far, James
M started some serious hacking on Maven builds, so I switched camps
and started cleaning up the core Maven build.
A Maven build for the site is on my to-do list, but as you've no doubt
noticed, I haven't had a whole lot of time to spend on it lately. I am
hoping to get back to it soon - perhaps this thread will be sufficient
as a nudge. ;-)
--
Martin Cooper
On Wed, 16 Feb 2005 10:42:36 -0800, Don Brown <mr...@twdata.org> 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
>
> Ted Husted wrote:
> > The best example of what I believe we want to do is the Jakarta Commons, which is Maven based.
> >
> > It might not be hard to add a Ant build file to Core to just build the web site, based on what is now over in Apps, or the build file from 1.2.
> >
> > It wouldn't have to build JARs, just run the XMLs through the Ant.
> >
> > Once we had the site building again, perhaps someone could add a section to the Roadmap on where we stand with this. There's been traffic on the list, but it's hard to keep up with the threads sometimes.
> >
> > My own preference would be to use Maven, but, in the end, them that does the work make the decisions.
> >
> > -Ted.
> >
> > On Wed, 16 Feb 2005 10:23:53 -0800, Don Brown wrote:
> >
> >> Ted Husted wrote:
> >>
> >>> 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: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
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.
The Core jars seem to build just fine (<yeah!/>), including the release target.
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.
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.
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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Don Brown <mr...@twdata.org>.
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
Ted Husted wrote:
> The best example of what I believe we want to do is the Jakarta Commons, which is Maven based.
>
> It might not be hard to add a Ant build file to Core to just build the web site, based on what is now over in Apps, or the build file from 1.2.
>
> It wouldn't have to build JARs, just run the XMLs through the Ant.
>
> Once we had the site building again, perhaps someone could add a section to the Roadmap on where we stand with this. There's been traffic on the list, but it's hard to keep up with the threads sometimes.
>
> My own preference would be to use Maven, but, in the end, them that does the work make the decisions.
>
> -Ted.
>
> On Wed, 16 Feb 2005 10:23:53 -0800, Don Brown wrote:
>
>> Ted Husted wrote:
>>
>>> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
The best example of what I believe we want to do is the Jakarta Commons, which is Maven based.
It might not be hard to add a Ant build file to Core to just build the web site, based on what is now over in Apps, or the build file from 1.2.
It wouldn't have to build JARs, just run the XMLs through the Ant.
Once we had the site building again, perhaps someone could add a section to the Roadmap on where we stand with this. There's been traffic on the list, but it's hard to keep up with the threads sometimes.
My own preference would be to use Maven, but, in the end, them that does the work make the decisions.
-Ted.
On Wed, 16 Feb 2005 10:23:53 -0800, Don Brown wrote:
> Ted Husted wrote:
>> 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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Don Brown <mr...@twdata.org>.
Ted Husted wrote:
> 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: dev-unsubscribe@struts.apache.org For
>> additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Building Struts Website
Posted by Ted Husted <hu...@apache.org>.
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. If the appropriate targets were put back into the Core build file, we could probably do that again on an interim basis.
Thought, if there's something simple you need to do, in a pinch, you could just patch the HTML, being careful to conform the source, which is still under Core.
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.
-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: dev-unsubscribe@struts.apache.org For
> additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org