nowaday, most packages are available in the public good (means maven.central). So (under the condition that you cutomers do have a medium ok connection) you could also just provide them with a small maven pom which does package all the 3rd party jars on their side. But maybe it's easier then to just burn a CD and send it over to them.
LieGrue, strub --- On Fri, 1/14/11, Kevin Meyer <[email protected]> wrote: > From: Kevin Meyer <[email protected]> > Subject: Re: Seperating into archives... > To: [email protected] > Date: Friday, January 14, 2011, 6:58 AM > Hi, > > Repacking all the archives into 3 archives was my way of > compromising > between bandwidth use and upgrade convenience. > > For total convenience, I would send the client a single > archive with > all dependencies - but this maximises the data footprint. > > To minimize data footprint, I could just send the > individual packages > that have changed, but this has a high workflow overhead > (on my side > I have to identify what packages are to be added and > removed, and this > must be repeated on the client site). > > An intermediate would be to "just" manage the 3 archive > packages > as listed. Then the client just needs to replace 1 (or 2 or > 3) of the > 3 packages. > > -- Mark: > Thanks for the advice. > > I must admit, maven certainly goes a long way to helping in > this > process. At the time when I had this problem, I think the > NOF was > using ant, and I was using Eclipse to build distribtion > packages. > I don't remember the full details anymore. > > Thanks, > Kevin > > > On Thu, January 13, 2011 13:57, Mohammad Nour El-Din > wrote: > > But if you have the problem with the bandwidth so why > you wanna make > > all in one archive ? IMHO I think you should make it > in separate > > archives and update only the archives you need to > update. > > > > >
