>While I'm sure there's some things that need updated, Fortress has been >mavenized for a while. I think the issue some people are having is the >fact >that most of our mavenized projects extend a base project.xml and custom >Avalon tools. What we may need to do is make sure each larger project >(like >Fortress, Phoenix, Framework, Merlin) can build independently without >having >to check out everything from CVS (which is the way the old ant scripts >worked).
When u are at the Fortress website and hit the download link it takes you to http://avalon.apache.org/download.cgi If you try to download the fortress binaries and unzip and run ant. It will fail. And can't build any examples. And there is no project.xml there. And try the same with the merlin binaries, everything works nice and clean. You guys understand the big picture here so can try alternatives. When someone comes to Avalon for the first time I don't know if the best thing for him to do is try building the source code from the CVS. And no complaints at all, you guys are doing a great job, these are just suggestions. -----Original Message----- From: Farr, Aaron [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 11:30 AM To: 'Avalon framework users' Subject: RE: Starting with Fortress (WAS: RE: Fortress: why is this) > -----Original Message----- > From: Vikas Phonsa [mailto:[EMAIL PROTECTED] > > That would be awesome. If you have an existing list of maven dependencies > by > any chance then pls post those. > > Vikas > > -----Original Message----- > From: hammett [mailto:[EMAIL PROTECTED] > > > Some said in the list that he is working to update > > that stuff. > > Yes.. I am "the one" :-) > > It will be mavenized till next monday. Umm... I just did a clean check out of the Avalon module (not just fortress), then ran "maven jar:jar" in the avalon/fortress/container directory and not only did everything build (downloaded the needed dependencies), but all the unit tests passed too. While I'm sure there's some things that need updated, Fortress has been mavenized for a while. I think the issue some people are having is the fact that most of our mavenized projects extend a base project.xml and custom Avalon tools. What we may need to do is make sure each larger project (like Fortress, Phoenix, Framework, Merlin) can build independently without having to check out everything from CVS (which is the way the old ant scripts worked). J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- 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]
