We have a bootstrap command that copies all libraries of hour maven assembly to a location in HDFS (actually, we use maven groupId and artifactId of our assembly in the hierarchical path to ensure each client has its jars on the backend avaiable of exactly the same assembly build).
We also use Grunt embedding instead of server embedding. Grunt has invaluable preprocessing capabilities compared to PigServer(). Basically we kickoff a java client that has grunt integrated and knows of its maven build number, so it knows what hdfs locations to pass on to pig for the jars. This is a little bit of a hack over Grunt but it's only perhaps a hunred lines longer than just do the same thing with a PigServer. -dmitriy On Wed, Jan 19, 2011 at 2:24 PM, Geoffrey Gallaway <[email protected]>wrote: > I'm looking for some suggestions and ideas for how to handle JAR > dependencies in a production environment. > > > * What do other people use to deploy their code to various systems? Check > in > jars with the code? Keep jars in a separate, network-based directory? > > Geoff > -- > Sent from my email client. >
