Repository updatePolicies are inverted

In axis2 parent's pom.xml, in the repositories section, the updatePolicies for releases/snapshots is reversed from what one would expect.

One would expect releases to be pegged at never (or at least less frequent) update policy, while snapshots would be always (or at least more frequent). This is because a release should be considered a static thing, and there should be no reason to update it once it's in a user's local repository, while snaps could be updated frequently.

Maybe repositories shouldn't be kept in the pom at all. The end user can always configure repos on their own machine; if there are concerns that a user wouldn't be able to download their needed deps from their already configured locations, instructions on how to update their settings could be provided. This would allow the user to decide their own update policies and would reduce the clutter of the pom file.