I would also recommend calling display-plugin-updates goal to look for dated maven plugins.
BTW. This mvn plugin works great (I use it all the time) but it isn't perfect due to the nature of maven. Periodically, someone needs to manually audit rice's dependencies. This is for a couple reasons:
1) It is pretty common that dependencies change name (groupId and/or artifactId) and the new versions under the new name will not show up in the report
2) Sometimes dependencies use non-standard version numbers where an older version is considered newer than a newer version
As a part of this audit I would also look at each module of rice and make sure it is declaring only the dependencies it is using. This way projects depending on rice are only bringing in what is required.
The following goals in the http://maven.apache.org/plugins/maven-dependency-plugin/ will address this concern. Again this isn't a perfect tool (there will be some false positives). You may consider publishing reports from some of these goals as well.