Chad -
I think I know what is going on now. This may be a small bug. If the maven andromdapp:generate cartridge were modified so that the above section had this instead match="^(alter table .* drop constraint|alter table .* drop foreign key|drop table)" (notice I added |alter table .* drop foreign key) then ALL of the initial lines would be commented out. The mySQL dialect uses "drop foreign key" rather than "drop constraint". If all of the initial lines were commented out, then the INITIAL maven create-schema would run without error. Once the database table has been created, one could comment OUT the entire <ant:replaceregexp section above, and subsequent re-builds of their project would result in the alter table and drop tables being executed (on what then would be pre-existing tables in the database. Make sense? BTW - is the "process" of using AndroMDA really that one should run maven drop-schema before ever "re-creating" it? If so, dis-regard the "one could comment out" comment above. I'm gathering that the author of this piece had no choice regarding the presence of the alter table and drop table lines in create-schema.sql (since they are generated by the hibernate SchemaExport process), so they simply opted to "comment out" that section once it was created. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2469#2469 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
