Hi Mike,
I am not sure how to use the new feature. Here is the parameters I
used to pass to eogenerator in WOLips:
-model "Resources/BlackPressDirectory.eomodeld" -refmodel "Resources/
Prototypes.eomodeld" -templatedir Templates -destination src -prefix
_ -filenameTemplate "{clas
sPackageName}{if isSuperclass}.base{endif}.{classNameWithoutPackage}"
-packagedirs -verbose -java -define-copyrightYear "2006" -define-
copyrightBy "Black Press"
I can find a way or reproducing most of them but how do I set
"prefix", "filenameTemplate", "packagedirs" and "verbose"
Also the settings "destination" and "subclass destination" are a bit
counter intuitive; I usually store my subclasses in a package
directory (com.blackpress.ldap in that case) and my generated classes
in a sub directory base inside the same package
(com.blackpress.ldap.base in that case). To achieve this I need to
put src in the destination and nothing the subclass destination.
I also think we need a way of forcing eogenerator to run when we are
doing a "full build" for distribution or release. I kind of liked the
idea of having it run whenever the model has changed even if I have
find it a bit unreliable.
How do you see the ant integration? instead of the xx.eogen file
could we make it a property file and have a target in the standard
build.xml to call eogenerator with those properties? May be in
woproject? That would save us from having to maintain two sets of
parameters.
Thanks for the work I think we are on the right track.
Pierre
On 15-May-06, at 11:09 AM, Mike Schrag wrote:
> The latest wolips (124) adds a little nicer support for
> EOGenerator. I went the route of how Eclipse supports .jardesc
> files for producing jar files. The first thing you should do is
> setup the fields in the WOLips=>EOGenerator preferences. Next, use
> the new EOGenerator wizard (under the WOLips section of the New..
> window), and fill in the attributes of your eogenerator
> configuration. To execute it, you can right-
> click=>WOlips=>EOGenerate... the file. I have not tried this on
> Windows at all, and I suspect there will be some escaping of
> backslash issues at the very least. You can have multiple .eogen
> files in your project if you have different sets of eogenerator
> configurations. It's a first-version, so bear with it :) I'm
> pretty annoyed with the file/folder selection dialogs that eclipse
> provides -- on the Mac, none of them appear to default to the
> folder that I specify, which is pretty annoying.
>
> One thing also is that if you change your global EOGenerator
> preferences after having created eogens, your .eogens will need to
> be updated (reopen, remove explicit references to default values,
> and resave). The eogen file itself is actually a one-line script
> that you can run from the shell also. I have no idea if this is
> useful to anyone. It makes life kind of annoying to maintain, so I
> might toss that if nobody has an opinion on it.
>
> ms
>
This archive was generated by hypermail 2.0.0 : Mon May 15 2006 - 18:26:19 EDT