Finishing up default value work
-Modifying test to demonstrate that ParsedFunctions or ConstantFunctions can be used where FunctionName parameters are requested.
closes #3047
Fixing up HeatSource in modules (inherits from BodyForce)
refs #3047
Miscellaneous DiracKernel improvements

* Storing a vector<Point> per Elem rather than a set<Point> for
  DiracKernels.  A std::set<Point> is always somewhat dangerous due to
  the floating point nature of operator< for Points.
* The DiracKernel object now uses two DiracKernelInfo objects to avoid duplicating code.
* Give DiracKernelInfo a more standard interface since it is used in a few more places now...
* Adding DiracKernel::hasPoint()
* Implement DiracKernelInfo::addPoint() in terms of DiracKernelInfo::hasPoint()
* Adding documentation.

Refs #2847.
Merge pull request #3095 from jwpeterson/dirac_set

Miscellaneous DiracKernel improvements
Merge pull request #3091 from permcody/default_values_final

Finishing up default value work
removed FunctionControlledDT.  I never use it, and it's rather inconvenient to use anyway compared with the MOOSE-supplied timesteppers, and it is untested
OrientedBoxMarkerDepr removed from Richards.  Use moose OrientedBoxMarker instead
Fixed #3046 .  Seemingly huge update with no functionality change - just cosmetic stuff.  Most of the work was doxygenating everything.  Also i made use of RangeCheckedParam whenever i could.  All auxvar/pp/fcn stuff is up-to-date with the new default-for-coupling.  However, i have NOT changed RichardsMaterial since i need to consider backwards compatibility, as mentioned in the comments to ticket #3046
Changed execution of material output and improved tests (#3096)
Separating NeighborCoupleable into its own file (closes #3110)
Merge pull request #3111 from andrsd/3110

Separating NeighborCoupleable into its own file (closes #3110)
Off-Diagonal Computation For Constraints

This adds off-diagonal computations to NodeFaceConstraints... allowing for an even more correct Jacobian.

closes #1476
Add methods to determine whether node or element is on boundary ref #3112

This adds MooseMesh::isBoundaryElem(), which is equivalent to
MooseMesh::isBoundaryNode().  Add two variants of this method: one to
determine whether the element is adjacent to any boundary, and one to
determine whether the element is adjacent to a specified boundary.  Also
add a version of isBoundaryNode() in which the boundary is specified.
Merge pull request #3101 from aeslaughter/material-3096

Changed execution of material output
Merge pull request #3113 from bwspenc/element_boundary

Add methods to determine whether node or element is on boundary
Merge pull request #3109 from WilkAndy/feature_3046

Feature 3046
Merge pull request #3108 from friedmud/constraint_off_diag

Off-Diagonal Computation For Constraints
Boundary restricted AuxKernels now working correctly
(closes #3114)
Added test for boundary nodal AuxKernels
(#3114)
Added elemental boundary AuxKernel test
(#3114)