Thanks, Eivind. I think I have a clearer picture of integration. The preferences and merge points allow me to run my code-generation multiple times without having to specify everything in the Ant file. Then at some point, I leave the Middlegen specific artifacts behind (pref and merge files) and work manually with the code that gets fed into the continuous-integration with XDoclet.
tim -----Original Message----- From: Eivind Waaler [mailto:[EMAIL PROTECTED]] Sent: Friday, February 21, 2003 10:28 AM To: '[EMAIL PROTECTED]' Subject: Re: [Middlegen-user] What's the Big Picture Hi there, some things have been implemented to help achieve a more "continous-integration" method of working with Middlegen. You might want to take a look at: 1. Preferences file. The changes you do in the GUI are saved to a preferences file. Check out samples/src/airline-prefs.properties for the example application. The location of this file is given by the prefsdir attribute of the middlegen ant task. Next time you run middlegen, your changes from last time should be in there. This file can be edited manually, or by opening the GUI again and making more changes. 2. Merge files. The code generated can be altered by adding merge files: http://boss.bekk.no/boss/middlegen/plugins/cmp20.html#example There are different kinds of merge files, take a look at them. Quite useful. Not very much is actually controlled by the ant build file. I think the preferences functionality should be the solution to your "issues" below. .eivind On Thu, 20 Feb 2003, Kuntz, Tim wrote: > I am looking at rolling out Middlegen to a team of developers at my company. > During my evaluation I have become a little confused as to the end-goal of > Middlegen. I guess my question is, "Is Middegen's focus on > continuous-integration or a one-time creation of source that gets fed into > the continuous-integration stream?". > > My observation is that in order to run Middlegen, I need to use Ant to > specify a majority if not all of the information required to generate the > sources. If I choose to display the GUI as the sample build file does, then > I can modify the Middlegen task settings prior to continuing with the code > generation, but the modifications I make are not saved to a new Ant build > file. So on the one hand, I have a Ant script that can be run again should I > add new tables or addtional plugins but it is not complete. On the other > hand, if I never plan on running that particular build file again I would > prefer just setting everything up in the GUI without having to know anything > at all about the underlying Middlegen task. > > Please, this is not a criticism of the project as I think it has evolved > nicely and I plan on using it as part of my development. I would just like > to know that any extensions I perform locally are not at odds with the > future direction or goals of the project. > > thanks, > tim > ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ middlegen-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/middlegen-user
