Any plans to use a different groupId, like org.apache.jakarta.commons
for artifacts deployed to m2 repos?
I've been seeing some really odd behavior caused by artifacts pulled
from an m1 repo for an m2 build. Specifically, in Geronimo we have
to pull some artifacts from the m1 repo, but since artifacts like
commons-logging 1.0.4 are in both, out m2 build starts complaining
about invalid poms because m2 downloads the m1 artifacts instead of
the m2 artifacts.
If the m2 artifacts had a different groupId this problem would go away.
Any plans to change the groupIds?
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
