configuration2 should use groupId org.apache.commons and an artifactId
of commons-configuration. I am not going to worry about configuration3
- we are still a long way off from completing configuration2.
Ralph
On Jun 22, 2009, at 3:22 PM, Emmanuel Bourg wrote:
Jörg Schaible a écrit :
Simply because the groupId change is a one time action only and
will not
scale for configuration3 ;-)
Bah, when Commons Configuration started, Maven didn't have groupIds,
there was a unique id. That was 5 years ago. Configuration 2 is far
from finished, Configuration 3 will certainly not happen before 5
more years. By that time the technical constraints will probably
change, and the issue will be solved differently.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
