Rolling the org.apache.commons groupId back to the individual component ids. It sounds as though we're not ready for the project.xmls to move to the new id. Intentionally leaving the pom.xmls as they are - sounds like when a component moves to maven-2, that that is when it should use the new groupId
Rolling the org.apache.commons groupId back to the individual component ids. It sounds as though we're not ready for the project.xmls to move to the new id. Intentionally leaving the pom.xmls as they are - sounds like when a component moves to maven-2, that that is when it should use the new groupId

git-svn-id: 94cad4ae0dfdbd5a35299816cdf961de95074614@479168 13f79535-47bb-0310-9956-ffa450edef68

apache/commons-dbcp,apache/commons-dbcp,apache/commons-dbcp