You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by ws...@apache.org on 2005/11/22 03:10:40 UTC
svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Author: wsmoak
Date: Mon Nov 21 18:10:31 2005
New Revision: 348065
URL: http://svn.apache.org/viewcvs?rev=348065&view=rev
Log:
Set up site address and directory to publish the site using Maven, and note how to build just the top-level site.
Added scopes to dependencies for Maven 2.
Modified:
struts/shale/trunk/build/README.txt
struts/shale/trunk/build/project.xml
Modified: struts/shale/trunk/build/README.txt
URL: http://svn.apache.org/viewcvs/struts/shale/trunk/build/README.txt?rev=348065&r1=348064&r2=348065&view=diff
==============================================================================
--- struts/shale/trunk/build/README.txt (original)
+++ struts/shale/trunk/build/README.txt Mon Nov 21 18:10:31 2005
@@ -32,6 +32,13 @@
$ maven multiproject:site
+To build the top-level site without the sub-projects, or the site for
+one of the sub-projects individually:
+
+ $ maven site
+
+ (The generated site will be in target/docs.)
+
Choosing a JSF Implementation
-----------------------------
Modified: struts/shale/trunk/build/project.xml
URL: http://svn.apache.org/viewcvs/struts/shale/trunk/build/project.xml?rev=348065&r1=348064&r2=348065&view=diff
==============================================================================
--- struts/shale/trunk/build/project.xml (original)
+++ struts/shale/trunk/build/project.xml Mon Nov 21 18:10:31 2005
@@ -46,10 +46,8 @@
<url>http://struts.apache.org/</url>
<issueTrackingUrl>http://issues.apache.org/bugzilla/</issueTrackingUrl>
- <siteAddress>struts.apache.org</siteAddress>
- <siteDirectory>
- /www/struts.apache.org/
- </siteDirectory>
+ <siteAddress>people.apache.org</siteAddress>
+ <siteDirectory>/www/struts.apache.org/shale/</siteDirectory>
<distributionDirectory>
/www/svn.apache.org/builds/struts
</distributionDirectory>
@@ -152,6 +150,9 @@
<artifactId>servlet-api</artifactId>
<version>2.4</version>
<url>http://java.sun.com/products/servlet/</url>
+ <properties>
+ <scope>provided</scope>
+ </properties>
</dependency>
<dependency>
@@ -159,6 +160,9 @@
<artifactId>jsp-api</artifactId>
<version>2.0</version>
<url>http://java.sun.com/products/jsp/</url>
+ <properties>
+ <scope>provided</scope>
+ </properties>
</dependency>
<dependency>
@@ -226,6 +230,9 @@
<artifactId>junit</artifactId>
<version>3.8.1</version>
<url>http://www.junit.org/</url>
+ <properties>
+ <scope>test</scope>
+ </properties>
</dependency>
<dependency>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
>
> > What would it take to accomodate Ted's request that the web site
> > subdirectory for Shale be "struts-shale" instead of "shale"? Is that
> just a
> > change to a single property someplace? (If so, could you go ahead and do
> > that ... then either you or I can add a redirect as well).
>
> Sorry, I didn't see his request. I can't change it from here, and I
> have class tonight. Quick fix on
> people.apache.org:/www/struts.apache.org :
> 1. mv shale struts-shale
> 2. add redirect to .htaccess
>
> This is the line in build/project.xml:
> - <siteDirectory>/www/struts.apache.org/shale/</siteDirectory>
> + <siteDirectory>/www/struts.apache.org/struts-shale/</siteDirectory>
OK, thanks ... I'll take care of it.
Craig
--
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
> What would it take to accomodate Ted's request that the web site
> subdirectory for Shale be "struts-shale" instead of "shale"? Is that just a
> change to a single property someplace? (If so, could you go ahead and do
> that ... then either you or I can add a redirect as well).
Sorry, I didn't see his request. I can't change it from here, and I
have class tonight. Quick fix on
people.apache.org:/www/struts.apache.org :
1. mv shale struts-shale
2. add redirect to .htaccess
This is the line in build/project.xml:
- <siteDirectory>/www/struts.apache.org/shale/</siteDirectory>
+ <siteDirectory>/www/struts.apache.org/struts-shale/</siteDirectory>
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
>
> $ cd shale/build
> $ maven multiproject:site site:sshdeploy
What would it take to accomodate Ted's request that the web site
subdirectory for Shale be "struts-shale" instead of "shale"? Is that just a
change to a single property someplace? (If so, could you go ahead and do
that ... then either you or I can add a redirect as well).
Craig
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/25/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
>
> > The 100 character messages seem to be coming from the [tar] task. Can
> the
> > plugin be told to use the Maven equivalent of Ant's longfile="gnu"
> > attribute?
>
> site:sshdeploy:
> [tar] Building tar:
> E:\svn\struts\current\shale\build\target\shale-1.0.0-dev-site.tar
> [tar] Entry:
>
> shale-clay/apidocs/org/apache/shale/clay/component/chain/class-use/AssignActionListenersCommand.html
> longer than 100 characters.
> [tar] Resulting tar file can only be processed successfully by GNU
> compatible tar commands
>
> As far as I can tell, it's just a warning that you need to use gnu tar
> on the server side. I checked and the files are getting updated.
Cool ... that is what I hoped it meant, rather than not including the file
at all.
Hoping to get through my test matrix and post an RC1 this evening ...
volunteers to help test it will be welcomed :-).
--
> Wendy
Craig
>
>
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
> The 100 character messages seem to be coming from the [tar] task. Can the
> plugin be told to use the Maven equivalent of Ant's longfile="gnu"
> attribute?
site:sshdeploy:
[tar] Building tar:
E:\svn\struts\current\shale\build\target\shale-1.0.0-dev-site.tar
[tar] Entry:
shale-clay/apidocs/org/apache/shale/clay/component/chain/class-use/AssignActionListenersCommand.html
longer than 100 characters.
[tar] Resulting tar file can only be processed successfully by GNU
compatible tar commands
As far as I can tell, it's just a warning that you need to use gnu tar
on the server side. I checked and the files are getting updated.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
>
>
> There's one issue in Clay: tar complains about a few files with a path
> longer than 100 characters. I think they're probably Javadoc pages
> that won't get updated.
Just did the site:sshdeploy for Shale ... cool :-).
The 100 character messages seem to be coming from the [tar] task. Can the
plugin be told to use the Maven equivalent of Ant's longfile="gnu"
attribute?
Craig
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/22/05, Martin Cooper <ma...@apache.org> wrote:
>
>
> I'm not sure which old days you're referring to here, but I don't recall
> the
> Struts web site *ever* being updated automatically. It has always been a
> manual process, unless I've missed some newer old days. ;-)
That matches my recollection as well :-).
I think, with the simplicty we have now (definitely easier than the old
days), we should just let the committer decide if his/her change is
significant enough to warrant updating the website. After all, if no xdocs
changes were checked in during a week, there wouldn't be any point to doing
the website update anyway :-).
--
> Martin Cooper
Crag
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, Ted Husted <te...@gmail.com> wrote:
> If someone wanted to set it up, I don't think it would be a bad thing
> for there to be a monthly sweep to catch anything we missed with
> ad-hoc updates.
Right now, I only trust 'maven site:sshdeploy' for Shale. I'll verify
the rest of the siteAddress and siteDirectory tags and will get
something in place to update the entire site from here, likely on the
weekend when I can keep an eye on it.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Ted Husted <te...@gmail.com>.
On 11/22/05, Ted Husted <te...@gmail.com> wrote:
> for there to be a monthly sweep to catch anything we missed with
/s/monthly/weekly
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Ted Husted <te...@gmail.com>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
> Interesting! It sure seemed like it... this was pre-1.1, when I was
> working with nightly builds and the website was always up to date with
> changes. Never mind, then. :)
I used to update it myself a lot, often as part of posting new
announcements. It might have seemed automated, but it was just
hard-working committers :)
If someone wanted to set it up, I don't think it would be a bad thing
for there to be a monthly sweep to catch anything we missed with
ad-hoc updates.
I know that now-a-days, I often don't send up more than the page I
changed, and it's easy to miss Javadoc changes.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, Martin Cooper <ma...@apache.org> wrote:
> I'm not sure which old days you're referring to here, but I don't recall the
> Struts web site *ever* being updated automatically. It has always been a
> manual process, unless I've missed some newer old days. ;-)
Interesting! It sure seemed like it... this was pre-1.1, when I was
working with nightly builds and the website was always up to date with
changes. Never mind, then. :)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Martin Cooper <ma...@apache.org>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/22/05, James Mitchell <jm...@apache.org> wrote:
>
> > It's a good idea at least to give it a once over by hand and make sure
> > everything was built correctly....especially if there are doc changes
> that
> > might cripple the site output.
>
> Whoever is editing files should be doing that.
>
> My read of the site plugin docs says that unless you configure it to
> 'clean', it won't remove files, it just adds and overwrites. And it
> may not even try the upload if the site build fails... I'll have to
> break one of the xdocs and see what happens.
>
> Bad content in otherwise well formed xml files will be caught when the
> commit message goes to the list, so...
>
> > If we wanted to automate this, we should at least provide ourselves a
> time
> > buffer to react to anything really bad.
> >
> > I suppose we could setup a weekly deployment from a staging site:
>
> IMO, a week is much too long. Back in the old days, the site used to
> get published nightly. I'm hoping that things get active enough
> around here that we'll need that again. ATM, I just want it. :)
I'm not sure which old days you're referring to here, but I don't recall the
Struts web site *ever* being updated automatically. It has always been a
manual process, unless I've missed some newer old days. ;-)
--
Martin Cooper
But I'm fine with publishing changes as needed, too -- especially now
> that it's a single command. Just having fun teaching Maven new
> tricks...
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, James Mitchell <jm...@apache.org> wrote:
> It's a good idea at least to give it a once over by hand and make sure
> everything was built correctly....especially if there are doc changes that
> might cripple the site output.
Whoever is editing files should be doing that.
My read of the site plugin docs says that unless you configure it to
'clean', it won't remove files, it just adds and overwrites. And it
may not even try the upload if the site build fails... I'll have to
break one of the xdocs and see what happens.
Bad content in otherwise well formed xml files will be caught when the
commit message goes to the list, so...
> If we wanted to automate this, we should at least provide ourselves a time
> buffer to react to anything really bad.
>
> I suppose we could setup a weekly deployment from a staging site:
IMO, a week is much too long. Back in the old days, the site used to
get published nightly. I'm hoping that things get active enough
around here that we'll need that again. ATM, I just want it. :)
But I'm fine with publishing changes as needed, too -- especially now
that it's a single command. Just having fun teaching Maven new
tricks...
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by James Mitchell <jm...@apache.org>.
We probably wouldn't want to do this nightly.
It's a good idea at least to give it a once over by hand and make sure
everything was built correctly....especially if there are doc changes that
might cripple the site output.
If we wanted to automate this, we should at least provide ourselves a time
buffer to react to anything really bad.
I suppose we could setup a weekly deployment from a staging site:
(weekly)
svn staging live
--- ------- ----
+-----scp------>|
+---maven-->| |
The process could send an email to the dev list that:
- a successful site was deployed
- a new site was deployed to staging that will go live in 7 days
(or something like that)
Your thoughts?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
MSN: jmitchell@apache.org
Skype: jmitchtx
----- Original Message -----
From: "Wendy Smoak" <ws...@gmail.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Tuesday, November 22, 2005 12:11 PM
Subject: Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt
project.xml
On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
> Oops ... that was it ... I was still looking in
> ".../struts/current/shale/target/docs".
>
> The inception year and the copyright owner were both missing ... if you
> look
> in the right place, of course, they're there.
Good. :) Maven does some odd things sometimes, but I was having
trouble explaining this one.
Double check that you've got the project.xml updates with the right
things in <siteAddress> and <siteDirectory>, and then try out 'maven
site:deploy' . Neat. :)
What do you think about adding this to the nightly build script?
$ cd shale/build
$ maven multiproject:site site:sshdeploy
There's one issue in Clay: tar complains about a few files with a path
longer than 100 characters. I think they're probably Javadoc pages
that won't get updated.
FTR: the site is being served directly from where ever
people.apache.org:/www/struts.apache.org is -- there's no delay at all
when you upload files.
--
Wendy
---------------------------------------------------------------------
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: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/22/05, Craig McClanahan <cr...@apache.org> wrote:
> Oops ... that was it ... I was still looking in
> ".../struts/current/shale/target/docs".
>
> The inception year and the copyright owner were both missing ... if you look
> in the right place, of course, they're there.
Good. :) Maven does some odd things sometimes, but I was having
trouble explaining this one.
Double check that you've got the project.xml updates with the right
things in <siteAddress> and <siteDirectory>, and then try out 'maven
site:deploy' . Neat. :)
What do you think about adding this to the nightly build script?
$ cd shale/build
$ maven multiproject:site site:sshdeploy
There's one issue in Clay: tar complains about a few files with a path
longer than 100 characters. I think they're probably Javadoc pages
that won't get updated.
FTR: the site is being served directly from where ever
people.apache.org:/www/struts.apache.org is -- there's no delay at all
when you upload files.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/22/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/21/05, Craig McClanahan <cr...@apache.org> wrote:
>
> > I use the "current" svn:externals thing as well, and run "maven site"
> from
> > the top-level Shale directory (the one containing the global
> > build.xmlfile). For me, that's at:
> >
> > /home/craigmcc/Apache/struts/current/shale
> >
> > However, I see the broken copyright from here,
>
> That's what I would expect. With no Maven build files in current/shale
> I'm surprised you get anything at all. All the maven commands need to
> be run from current/shale/build or somewhere beneath it.
>
> > or from the "build" directory below it:
> >
> > /home/craigmcc/Apache/struts/current/shale/build
> >
> > Same problem if you run "maven multiproject:site" from here ... just
> takes
> > longer to see it :-).
>
> And you're looking at the results underneath 'build', in
> /home/craigmcc/Apache/struts/current/shale/build/target/docs ?
Oops ... that was it ... I was still looking in
".../struts/current/shale/target/docs".
Is the missing inception year the only thing that's wrong?
The inception year and the copyright owner were both missing ... if you look
in the right place, of course, they're there.
Craig
At this point I usually start checking plugin versions. I have
> maven-site-plugin-1.6.1 and maven-xdoc-plugin-1.9.2, both of which are
> the latest. (I'm looking in 'cache' under my m1 repository... I've
> moved mine, but I think the default is: ~/.m2/repository/ .)
>
> Or just download them with:
> maven plugin:download -DgroupId=maven -DartifactId=maven-site-plugin
> -Dversion=1.6.1
> maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin
> -Dversion=1.9.2
>
> This is strange, though. Maybe redirect the output and send me the
> log? If you do that, I'd like to see 'maven site' and 'maven site -X'
> separately.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/21/05, Craig McClanahan <cr...@apache.org> wrote:
> I use the "current" svn:externals thing as well, and run "maven site" from
> the top-level Shale directory (the one containing the global
> build.xmlfile). For me, that's at:
>
> /home/craigmcc/Apache/struts/current/shale
>
> However, I see the broken copyright from here,
That's what I would expect. With no Maven build files in current/shale
I'm surprised you get anything at all. All the maven commands need to
be run from current/shale/build or somewhere beneath it.
> or from the "build" directory below it:
>
> /home/craigmcc/Apache/struts/current/shale/build
>
> Same problem if you run "maven multiproject:site" from here ... just takes
> longer to see it :-).
And you're looking at the results underneath 'build', in
/home/craigmcc/Apache/struts/current/shale/build/target/docs ?
Is the missing inception year the only thing that's wrong?
At this point I usually start checking plugin versions. I have
maven-site-plugin-1.6.1 and maven-xdoc-plugin-1.9.2, both of which are
the latest. (I'm looking in 'cache' under my m1 repository... I've
moved mine, but I think the default is: ~/.m2/repository/ .)
Or just download them with:
maven plugin:download -DgroupId=maven -DartifactId=maven-site-plugin
-Dversion=1.6.1
maven plugin:download -DgroupId=maven -DartifactId=maven-xdoc-plugin
-Dversion=1.9.2
This is strange, though. Maybe redirect the output and send me the
log? If you do that, I'd like to see 'maven site' and 'maven site -X'
separately.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/21/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 11/21/05, Craig McClanahan <cr...@apache.org> wrote:
>
> > > + $ maven site
> >
> > I notice that when I do this in the Shale top-level directory, you get
> an
> > incomplete copyright notice:
> >
> > (c) -2005,
>
> From the Shale top-level directory, as in /struts/current/shale/ ?
> There is no Maven build file there, so no <inceptionYear> for it to
> use. If it's working at all it's only by virtue of 'xdocs' being
> Maven's default location. I get an error from the xdoc plugin if I
> try it from there.
>
> /svn/struts/current/shale/build
> $ maven site
>
> works for me, and builds only the top section of the site. Let me
> know if you're seeing something different.
I use the "current" svn:externals thing as well, and run "maven site" from
the top-level Shale directory (the one containing the global
build.xmlfile). For me, that's at:
/home/craigmcc/Apache/struts/current/shale
However, I see the broken copyright from here, or from the "build" directory
below it:
/home/craigmcc/Apache/struts/current/shale/build
Same problem if you run "maven multiproject:site" from here ... just takes
longer to see it :-).
Craig
--
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/21/05, Craig McClanahan <cr...@apache.org> wrote:
> > + $ maven site
>
> I notice that when I do this in the Shale top-level directory, you get an
> incomplete copyright notice:
>
> (c) -2005,
>From the Shale top-level directory, as in /struts/current/shale/ ?
There is no Maven build file there, so no <inceptionYear> for it to
use. If it's working at all it's only by virtue of 'xdocs' being
Maven's default location. I get an error from the xdoc plugin if I
try it from there.
/svn/struts/current/shale/build
$ maven site
works for me, and builds only the top section of the site. Let me
know if you're seeing something different.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: svn commit: r348065 - in /struts/shale/trunk/build: README.txt project.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 11/21/05, wsmoak@apache.org <ws...@apache.org> wrote:
>
>
> +To build the top-level site without the sub-projects, or the site for
> +one of the sub-projects individually:
> +
> + $ maven site
Wendy,
I notice that when I do this in the Shale top-level directory, you get an
incomplete copyright notice:
(c) -2005,
whereas it seems to work correctly when you build the entire site. Is that
an artifact of something not getting inherited when you do just the
individual sites?
Craig