Also, because maven-rio-plugin doesn't reference its parent a new
developer can't build Rio from the root without first building
maven-rio-plugin. It can't be resolved by the other modules that
depend on it. Again, was this by design or would a small patch be in
order? (Again, I can do it. Didn't want to create a Jira ticket if
there was a reason why things are the way they are.)
-jeff
Dennis
-jeff