Now that there are changes to RunJar, for trunk, can you move RunJar to mapreduce from common
Sure thing. I'll take care of that when I post the patch for trunk.
Thanks! Please also make sure the new class in mapreduce is in org.apache.hadoop.mapreduce.util and create a deprecate class in org.apache.hadoop.util which uses functionality from org.apache.hadoop.mapreduce.util.RunJar.
Do you see any use for filters here beyond a straight regex? We can express the old behaviour as /./ and the new behavior as /^(lib|classes)\//.
Yes, that should do, I think.
Also, I'd prefer to make this an *undocumented configuration parameter, since I think there is very little use for the old version and we don't want to encourage people to abuse this.
Agreed. Even now, it is undocumented, AFAIK. A more appropriate reasoning for making it a configuration is that some users may want directories other than lib or classes to be unjarred.
Would you see this being used as a per-job option or a TaskTracker-scoped option?
Per-job. By the time, we un-jar stuff on the TT, job configuration is already localized, so it's easy to get this option just before un-jarring.