Limited tests to allow threading target to pass (refs #4109)
Use the new MeshBase::get_boundary_info() API in libmesh.

Refs libMesh/libmesh#388.
Reduce the number of times we call get_boundary_info().

Generally clean up some code.

Refs libMesh/libmesh#388.
No reason to have one random templated function defined in the header file.

Refs #3544.
Fix bug where SetOrigin() used xmin for all three components.

This may have worked because the only tests which used origin
explicitly set it themselves rather than getting it from the Mesh.

Refs #3544.
Removed an errant input file that I found in the stack directory.

Refs #3976.
Add 3D mesh generation capability to ImageMesh

The implementation is currently based on ImageFunction's, but we
accept slighly more irregular input without erroring out.  ImageMesh
will eventually provide the stack of filename strings to
ImageFunction, and thus ImageFunction will require an underlying
ImageMesh to work.  Note that ImageMesh still does not depend on VTK,
but it could if our simple 'file' command approach is found to be
insufficient.

Refs #3976.
Adding a test of 2D and 3D ImageMesh.
Added a 'cap' type of smoothing to WeakPlaneShear

Added two tests demonstrating the idea and its correctness

Also modified MohrCoulomb and WeakPlaneTensile to remove unused variables

Addresses #4125 .
Note that i intend to do the same 'cap' stuff in MohrCoulomb and Tensile at some stage soon.
MooseSharedPointer should use .get()
(refs #4024)
Comparisons on shared pointers need .get() called

Refs #4042
Merge pull request #9 from andrsd/null-shared

Comparisons on shared pointers need .get() called
Removed restriction for time_integrator test
(refs #4109)
Oops! wrong one
Merge pull request #4127 from aeslaughter/null-shared

MooseSharedPointer should use .get()
Merge pull request #4110 from aeslaughter/implicit-euler-4109

Limited tests to allow threading target to pass
Only remove the mesh and equation systems file on rank 0 (thread 0)
closes #3992
Show the user a better value
closes #4121
Adding FileRangeBuilder utility functions.

These allow the user to avoid duplicating input file parameters that
are shared between ImageMesh and ImageFunction.  This also has the
benefit of putting all the file range argument parsing code in one
place.

Refactored the ImageFunction so that it uses its own file range
parameters when they are available, and pulls from the ImageMesh when
they are not.

@aeslaughter

Refs #3976.
Merge pull request #4128 from permcody/restart_fix

Restart fix