Commons components use two different styles of groupId: commons-<component> - used by some original components (e.g. IO, NET) org.apache.commons - newer style, used by most components
Since Commons Parent uses the latter, and the groupId is inherited, in theory a component using the new groupId does not need to specify it. However, I think that is unwise, as it's not clear whether the omission is deliberate or accidental. Also the parent could potentially be changed to one with a different groupId. Far better to specify the groupId explicitly rather than relying on an inherited default. Agreed? S. P.S. Note that changing the groupId can only be done if the package name is also changed, see https://wiki.apache.org/commons/MavenAndClasspath --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
