Mike - thanks for taking the time to explain this to me. I still have a few hangups and just posted a few follow up questions to Matt. But basically what still confuses me is the 'all or nothing' approach of mvn war:inplace - once I run this I basically get the *entire* appfuse source tree and it's back to managing everything. If I only want to override one file (e.g. mainMenu.html) then how do I only get that? Or do I just 'steal' a copy from the deployed directory and copy it in my source tree? At that point will my new version override the original one?
I'm just trying to fully understand the paradigm here, what you guys are doing is very exciting. Michael ----- Original Message ----- From: Michael Horwitz To: [email protected] Sent: Friday, January 26, 2007 1:06 AM Subject: Re: [appfuse-user] appfuse 2.0 only skeleton? Hi Michael, The answer is yes and no - AppFuse 2.0 is designed to be really, really thin. You inherit the core functionality using Maven, and only replace that which you need. It uses war overlaying (see http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html) to pull in the AppFuse core. The idea is that your project will only contain your files, or the files you choose to override from AppFuse. Keeps things a little lighter and cleaner! If you run mvn install and look in the target directory you will see that a fully fledged war file is built that contains your pages,classes and resources merged in with those supplied by AppFuse. The driving force behind this design is to try and isolate your changes from the AppFuse core, which will hopefully make it much easier for you to upgrade from one version of AppFuse to another. As always you are free to change/override anything you want. So if you want to seed your project with the contents of your chosen AppFuse web framework build, simply run mvn war:exploded (at the root of your project if you used a basic archetype, and in the web module if you used a modular archetype). After doing this you should delete the WEB-INF/lib and WEB-INF/classes directories from the source webapp folder. For other possible changes, please take a look at the tutorials on the AppFuse website - hopefully they will make it all a little clearer. Happy AppFuse developing! Mike On 1/25/07, Michael Mehrle <[EMAIL PROTECTED]> wrote: Hi Mike - this is actually the one I installed - the database is being created and all but there is only one single class in each package. Please let me know if I'm missing something here - I just read through the quickstart tutorial again and it seems that I followed the instructions properly. Thanks, Michael ----- Original Message ----- From: Michael Horwitz To: [email protected] Sent: Thursday, January 25, 2007 3:21 AM Subject: Re: [appfuse-user] appfuse 2.0 only skeleton? Hi, M2 of AppFuse 2.0 has been released, and you are encouraged to have a look at it. When you set up a new project using the archetype, it will have very little in it. This is by design - Maven will weave in the rest. If you build and deploy an application from the archetype you will see that it is a fully fledged AppFuse project. Please see the QuickStart guide and related tutorials to get going: http://www.appfuse.org/display/APF/AppFuse+QuickStart Mike. On 1/25/07, molecool <[EMAIL PROTECTED] > wrote: Sorry if I'm asking the obvious but knowing the 'old' appfuse I realized that the 2.0 implementation only has a 'hello world' class. When is this going to be fleshed out? I've gotten used to maven and would like to use 2.0 since I'm just getting started on a new project. Would hate having to use 1.9.x now and then have to upgrade in a few weeks when it's 'officially' being released (Matt mentioned February?). Anyway, if there's an 'early developer' build I'd like to get my hands on it. Cheers, Michael -- View this message in context: http://www.nabble.com/appfuse-2.0-only-skeleton--tf3096058s2369.html#a8595531 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
