> 1) Since many files seems not changed (I think so) during the > migration of versions (eg.postgresql-8.1-407.jdbc3.jar) we can > distribute as NB only the files which had a change together with a txt > file which explain how to construct the most recent OJ NB working. > This save space on the web. > I don't see the need for this, it would be a complicated process to setup and to ensure that all the right files are distributed. I know this cause I have to do it for one of my clients projects and it causes a lot of problems. Also doing it that way means a user would have to download all the patches to get the latest version which may not be possible if say their last nightly build download was from 20 days ago.
The build is setup to only keep a certain number of previous builds so it won't take up too much disk space. For users who don't want to have to download too much in one go they can just use SVN to get the source and then do mvn install to compile their own version. Paul ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
