> > I want to customize the package structure of the generated > files. For > > instance I want the Spring cartridge to create the implementation > > classes in a distinct "impl" or "hibernate" subpackage. > > > > I understand people tend to work like this but it is a bad > practice, impl classes belong in the same package (not > necessarily in the same directory) > > 'impl' and 'hibernate' subpackages only make sense when you > want to provide an API to your users, and 'implementation' > and 'hibernate' are part of the deliverables, business-wise that is > > I learned in fact, that it is much easier to use the packages > that are constructed by AndroMDA, because they map directly > onto the design/achitecture .. in my IDE it's more natural to > look for stuff (less opening/closing tree nodes, less scrolling) > > but again: it's up to you, you probably have a good reason > like compatibility with legacy apps or something, so it might > still be interesting for you to actually proceed this way...
OK, I see your point. But when I have to explain the project structure to other people (for instance new developers taking over the job) I find it much easier, when implementation classes (which are not relevant for understanding the business logic) are hidden in subpackages. Well, agreed, now with AndroMDA I have fancy and uptodate UML diagrams which can be used to learn about the project. But still many people immediately want to take a look at the sources. In my opinion it still would be nice to be able to customize the package structure gracefully, but I can definately live with the situation. > > > > I can accomplish this by changing the andromda-cartridge.xml in the > > jar-file. But I don't like to customize the cartridge every > time a new > > version is released. > > > > Therefore I tried the "mergeLocation" feature, but > obviously I cannot > > override the andromda-cartridge.xml (only templates). > > > > are you sure this does not work ? I never actually tested it > myself but give it a try (remember to reconstruct the > directory structure from the root of the JAR file) > Yes, I unzipped the complete cartridge and also patched some templates, which worked (in contract to the cartridge descriptor). by the way I realized that it's not sufficient to change the cartridge descriptor, I also have to change the package declaration in the templates... ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
