Tim, Thanks for the patch. I took a look, and it will certainly help. There are a few more things that need to be tackled before we're ready to create the distribution with Maven.
1. Generate the TLD files (& docs) 2. Run the Cactus tests 3. Build the web apps 4. Migrate the documentation Inspired by your patch, I realize that we might be able to do some of that by calling Ant tasks. It does raise one question about Maven. If we still have to write Ant tasks, is there enough benefit in switching to Maven? We'll see how it shakes out :-) Steve > -----Original Message----- > From: Tim Chen [mailto:[EMAIL PROTECTED] > Sent: November 30, 2003 9:01 PM > To: 'Struts Developers List' > Subject: RE: Maven test run > > > As a Struts user I would rather not wait for the mavenization > to hold up > the 1.2.0 release niether. > As a Maven user though I can get the Struts release packages to look > just like the awesome release target that Martin built for the ant > process (Look at my maven.xml patch in bugzilla for an > example on how to > get maven's default dist target to do what we like). I'm kind > of having > a hard time finding time to do it right now but I'm sure it would be > ready for the next Struts release (after the initial 1.2.0 release :)) > Currently I can 'hack' the release to look identical to the current > release but I didn't want to do that just so that we can use maven to > build a release. > I agree that the web apps and contrib needs to be separate > projects but > since I'm not a maven expert, I don't know what the 'best > way' of doing > things are. So if someone has an opinion about it.. please speak up. > > Thanks, > Tim Chen > [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
