commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject [ALL] explicit Maven groupId in component POMs
Date Fri, 21 Apr 2017 13:12:39 GMT
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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message