The location is currently: http://svn.apache.org/builds/struts/maven/trunk/docs/
So, we will get (almost) instant feedback for changes. I know this goes against our "site will be as of the latest release" strategy, but it works for me....for now. Maybe we can call it "staging" or something.
We should set out a plan to move from our existing site to the Maven generated one. I know there are some of us who are opposed to this, but it really would be the best for each subproject.
One of the goals of the reorg was to allow any single subproject to release independently of the rest. Doing so with such fragmented docs is difficult if not impossible. Getting all the crossrefs fixed and published....ugh. That's the great thing about Maven's multiproject goals. This stuff is so exciting! There are many great things coming!
-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED]
----- Original Message ----- From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Tuesday, April 05, 2005 12:38 PM
Subject: Re: Nightly builds - short term plans
On Apr 5, 2005 8:51 AM, James Mitchell <[EMAIL PROTECTED]> wrote:
Ok, I think I've got it right (finally ;)
The nightly process is kicked off at 4AM EST. There are 2 parts to the build.
1st is the Maven build against the latest from current/ (head), 2nd is to
build the latest from the 1.2.x branch ( STRUTS_1_2_BRANCH) and includes the
artifacts from (essentially) doing a "ant release" (now including
contrib/el).
I made changes to the ant build scripts to download the dependencies and use
them as part of the build instead of being forced to setup a
build.properties (I am so over that ;)
There's still a lot of work to be done over in current/trunk and here's what's in my freetime queue:
- get current/apps building correctly (needs a src distribution). I've got a few ideas, but it will likely mean more refactoring.
- Add shale to the nightly build process (non-intrusive)
- I am in the middle of a huge refactoring effort for the taglib tests. I would like to see 100% coverage and a Clover report to prove it.
- Figure out what to do about the docs/xdocs dilemma
I'm actually working on the docs at the moment, albeit slowly since I don't have oodles of spare time right now. I'm splitting up what's currently under 'core' into a top level site, a core site, and bits that will go into other subprojects, and I'm moving it to Maven xdocs. Maven's current default L&F isn't my favourite (I preferred the previous one), but we can futz with that later if we want.
A secondary goal, in my mind at least, is to come up with a good way to distinguish between docs and site, and to move away from the docs / site as a war file the way we have it now. I haven't thought too much about this yet, so any ideas would be welcome.
Not much is done yet, other than a very bare-bones top level site, so if this isn't the way folks want to go with the docs / site, now would be a good time to say so. ;-)
-- Martin Cooper
(...there are many more items on my list, but these are forefront at the moment)
-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
