fix google java style guide issues

fix all google style guide issues except the
ones for variable names that have to follow
'^[a-z][a-zA-Z0-9]*(_[a-zA-Z0-9]+)*$' because
we need to have certain variables match windows
lettering precisely.
update build.xml to be like other adaptors'

DB LDAP AD and SP build.xml are very similar.
Making FS be as similar.
During this process noticed that FS build.xml
file had confusion between adaptor.version and
adaptorlib.version .
Fix b/16198970: Config option to skip reading share ACL

The adaptor attempts to preserve access control integrity when sending
Access Control Lists (ACLs) to the GSA. In general, only users that have access
to a file share have access to the files maintained on that share, so the
adaptor includes the share's ACL in those sent to the GSA.  However, in some
configurations, the adaptor may not have sufficient permissions to read the
share ACL. In those instances, the broken share ACL will prevent all files
maintained on that file share from appearing in search results. The GSA's
Index Diagnostics for those will also indicate a broken inheritance chain.

If the share ACL cannot be read by the adaptor, the administrator may
skip the attempt to read the share ACL by setting the
'filesystemadaptor.skipShareAccessControl' configuration option to 'true'.
This feeds a highly permissive share ACL to the GSA, rather than the actual
share ACL, leaving only the file system ACLs to control access.

WARNING: Bypassing the file share access control may be inconsistent with
enterprise security policies. This may allow users that do not have access
to the file share to see documents hosted by that file share in search results.

Code Review:
http://codereview.appspot.com/123780043
Fix b/17116680: Change log level for unresolvable SIDs to FINEST"

Code Review: http://codereview.appspot.com/133730043
Fix WindowsAclViews test failures

There are some test failures on the 32-bit platforms.
It seems the tests were having some issues serialzing and deserialzing
SIDs correctly. This does not appear to be a 32-bit issue, so much
as a GC issue. It looks like the SIDs were getting garbage collected
because the only reference to them was a serialized Pointer in the
ACE.

This change adds caching of SIDs in a HashMap to the tests to avoid
serializing and deserializing of SIDs.

Code Review: https://codereview.appspot.com/132800043/
allow customers to turn off monitoring

it appears that monitoring and collaborative excel use
conflict making excel files difficult to save. for time
being allowing user to disable monitoring.
Change submodule to point to library on github
Fix b/16286865: NPE when configured against DFS namespace.

The adaptor made the assumption that if the path returned by
getDfsUncActiveStorageUnc() was different from the path supplied
to that method, then a DFS link had been resolved; otherwise it
assumed that the supplied path did not represent a DFS link.

However this assumption was flawed. In most cases, passing in
just the namespace (\\server\namespace) would indeed return
that same path.  But in other cases, hostname normalization
would occur, returning something like \\SERVER\namespace or
\\server.mydomain.com\namespace.  The returned strings were
different, even though no link had been traversed.

The DFS_INFO_3 structure returned from GetDfsInfo() does
contain flags indicating whether the path is a DFS root or
a DFS link.  I added 2 methods to the FileDelegate interface,
isDfsRoot() and isDfsLink(), and renamed getDfsUncActiveStorageUnc()
to the less awkward resolveDfsLink().  I then modifed FsAdaptor
make no assumptions about whether a link had been resolved.

Finally, I added unit tests for the new methods, and updated
the test infrastructure to accomodate the underlying DFS root flags.

Code Review: http://codereview.appspot.com/156080043
Fix b/16619976: Adaptor feeds improper DFS share ACLs

DFS configuration allow the administrator to set explicit
permissions on DFS links.  The adaptor now checks for explicit
permissions returned from DfsGetInfo level 150.  If explicit
permissions were provided, they will be fed as the DFS share ACL.
If not specified, we fall back to the permissions on the namespace
root as before.

Code Review:  http://codereview.appspot.com/169840043
update plexi library pointer