Part of the problem with tracking down an issue with Google Maven was
that its behavior was too different from other package managers when it
didn't need to be. This gets Google Maven using more of the existing
infrastructure rather than inventing its own. It also cleans up some
additional API cruft, making method usages more consistent (even if
their parameters coming in are a little odd).
Part of the problem with tracking down an issue with Google Maven was that its behavior was too different from other package managers when it didn't need to be. This gets Google Maven using more of the existing infrastructure rather than inventing its own. It also cleans up some additional API cruft, making method usages more consistent (even if their parameters coming in are a little odd).