|
From: Mark R. D. <mdi...@la...> - 2003-01-10 19:03:18
|
I was thinking just versioned releases would probibly be enough. Primarily just as an alternative for deploying RePast. If you provided the repast.jar via a consistent http url, then build scripts for binary versions could just get that jar along with the other third party stuff via ant. The logic of this is: Often when your trying to allow others to run your model, you don't neccessarily want them to have to go through and entire build or install process independently to get RePast on their client. As all the support for running the model is either in repast.jar or third party jars, then it would be logical to provide downloadability for the repast.jar if your going to do it for third party jars. -Mark Thomas R. Howe wrote: >Do you mean nightly builds? I hadn't thought about it, but I suppose we >could do that. > >-Tom > >On Thu, 2003-01-09 at 21:49, Mark R. Diggory wrote: > > >>Thomas R. Howe wrote: >> >> >>>The ant build file will now fetch the third party jars as part of the >>>build process, so hopefully, an entire distribution can be built quickly >>>from this new structure. >>> >>> >>> >>Great, I'm looking forward to this. Are you going to release locations >>for first party repast jars as well as third party jars? >> >> >> >> >> >>------------------------------------------------------- >>This SF.NET email is sponsored by: >>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >>http://www.vasoftware.com >>_______________________________________________ >>Repast-developer mailing list >>Rep...@li... >>https://lists.sourceforge.net/lists/listinfo/repast-developer >> >> |