Null handling for entry.getMsg()

Without this null check, a null msg will cause an NPE which travels up and aborts the entire TokenMacro.expandAll call.   As a use case, the Jenkins Accurev SCM plugin will produce this (literal null) if a commit msg is not provided by the user:  

"changeSet" : {
    "items" : [
      {
        "affectedPaths" : [
          "foo/bar/Baz.java"
        ],
        "author" : {
          "absoluteUrl" : "http://someurlhere/whatever",
          "fullName" : "Mr FooBar"
        },
        "commitId" : null,
        "msg" : null,
        "timestamp" : -1
      }
    ],
    "kind" : null
  }
Merge pull request #70 from fooshards/master

Token Replacement fix