Just a quick tip. If your box is setup to run Model-Glue2 already, you probably have a ColdFusion mapping set up for ModelGlue that points to the V2 framework. If you want to play with V3 but not mess up your V2 sites (not to imply Joe is anything less than perfect), then consider this simple tip.
Make a new instance of the application template, then open up Application.cfc and add this:
<cfset this.mappings["/ModelGlue"] = "/Users/ray/Documents/workspace/ModelGlue3/trunk/ModelGlue/">
Of course you would edit the path to point to the right folder. This will overrule the ColdFusion Admin's mapping and use a model specific to the application. Of course, this requires ColdFusion 8.
Archived Comments
This was another query I wanted to ask you.
Yup, that concept bit me hard on me first deployment of an application.cfc... I didn't realize that I was going to lose some predefined mappings, and it took me at least a week and then an Aha! moment to realize that I could mold my own mappings. That alone was worth a 5 minute happy dance.