> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jonathan > Carlson > Sent: Wednesday, March 26, 2003 9:35 AM > To: [EMAIL PROTECTED] > Subject: [Andromda-user] minor sample usability issues from CVS > > > FYI > > The LAN group here finally got port 2401 opened for me so I'm using the > code from CVS and... > > 1) The build.properties for the car-rental-system appears to be > needlessly complex.
agreed > > 2) The car-rental-system/build.properties is looking for the > andromda.jar file in the $andromda.home directory instead of the > andromda.home/build/ directory. > The AndroMDA distribution and the CVS directory structure are slightly different. In the distribution the sample is located at: andromda/sample In CVS the sample directory is located at: andromda/src/sample The way I did things in the past was I would build AndroMDA from CVS and then point my AndroMDA home to: andromda/dist/predist That way I end up using a directory structure exactly like the distribution structure. The build could certainly be improved. > 3) I'm getting these errors when running the deploy target for the > car-rental-system build.xml: > > The import org.andromda.core.dbmapping.Mapping cannot be resolved > The import org.andromda.core.dbmapping.Mappings cannot be resolved > The import org.andromda.core.dbmapping.SqlType cannot be resolved > This makes me think your AndroMDA build did not work properly and this is probably because different locations of the sample directory in the distribution and CVS. > I found these files in the andromda/build/gensrc directory, and I'll > look further into the underlying cause, but my 2 cents is that getting > the sample to run should be very straightforward, which this doesn't > appear to be. Maybe there is a difference between the distribution file > layout and the CVS layout, but it probably should work similarly easy > either way. A readme file would help, but I think it could be simpler > to run as well. > Getting the sample running from the distribution files I think is relatively straight forward - except that I agree the build.properties file is needlessly complex. I think it is the building of AndroMDA from CVS that you are having problems with. Hopefully we will improve this before the next release (beta?). > Thanks again for a great tool (even if it's still a work-in-progress > :-), > > Jonathan Carlson > Minneapolis, Minnesota > > > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ********************************************************************** > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > _______________________________________________ > Andromda-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
