Yeah, I remember that now, will resume using that trick. But also: Monster Jars Considered Harmful, so I should dredge up a deploy flag or something which allows us to run seamlessly with small jar + libjars instead (so people [incl. me] can tack on their own jars by modifying the libjar classpath instead of having to modify the build itself).
On Fri, Jul 5, 2013 at 1:29 AM, Ted Dunning <[email protected]> wrote: > I find that rsync -zav does wonders on sending monster jars. It seems to > understand small changes in the jar and only sends a small amount of data. > > Never have dug into why. It just seems unreasonably efficient to be > otherwise. > > > On Fri, Jul 5, 2013 at 1:23 AM, Jake Mannix <[email protected]> wrote: > > > I forget, I know our "default" deployment is via the shaded monojar, but > do > > we also have an option somewhere to allow running with --libjars instead? > > Much more rsync-friendly for rapid prototyping (esp. when on slooooow > > remote connections). > > > > -- > > > > -jake > > > -- -jake
