We don't force the package name as groupId, but the "expected" package
name. eg. junit is in package junit but we'd put it in org.junit.
After that is up to the organization (apache) to decide how org.apache
is splitted.
Now from the apache side ;) sounds like a groupId per PMC is a good
idea, and
On 3/3/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Now answering on the new thread with less spelling errors :)
>
> Henri Yandell wrote on Friday, March 03, 2006 6:40 AM:
>
> > Re-subjecting this - bit hidden under the old subject.
> >
> > On 3/2/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> >>
Now answering on the new thread with less spelling errors :)
Henri Yandell wrote on Friday, March 03, 2006 6:40 AM:
> Re-subjecting this - bit hidden under the old subject.
>
> On 3/2/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
>> On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>>>
>>>
Re-subjecting this - bit hidden under the old subject.
On 3/2/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
> > If we start to add m2 poms to SVN I do think we should use the Maven 2
> > way to declare groupId, like this:
> >
> >org.a
