I think commons is required or the group would get too big. Also a
groupId per PMC sounds the best approach.
On 3/3/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> Another one:
>
> org.apache.jakarta
>
> no commons.
>
> With my different hats/mental viewpoints:
>
> * Foundation: We need to have an
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:
> >>
Another one:
org.apache.jakarta
no commons.
With my different hats/mental viewpoints:
* Foundation: We need to have an organizing, pmc based structure.
* Jakarta: We need a single top grouping for Jakarta
* Commons: We need a grouping for Commons
* Jakarta: I want to merge Commons and Jakarta,
I'd say o.a.j.c, but really it doesn't matter. Pick one and use it
consistently.
If you use o.a.c, you will have to share with anything else "commons" at
Apache. Same deal that has been traded off for the Java package before.
It's really not a big deal.
- Brett
Dennis Lundberg wrote:
> Henri Yan
Henri Yandell wrote:
On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact this list a
Jörg Schaible wrote:
Hi Henri,
Henri Yandell wrote on Friday, March 03, 2006 5:33 AM:
On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary
Henri Yandell wrote:
On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact thi
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:
>>>
>>>
Hi Henri,
Henri Yandell wrote on Friday, March 03, 2006 5:33 AM:
> On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>> Alex Karasulu wrote:
>>> Hiya,
>>>
>>> The directory project depends on commons-daemon 1.0.1 and we had to
>>> update the maven2 repo with a temporary pom.xml to allow our
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
On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Alex Karasulu wrote:
> > Hiya,
> >
> > The directory project depends on commons-daemon 1.0.1 and we had to
> > update the maven2 repo with a temporary pom.xml to allow our recent
> > release to go through. I wanted to contact this list and m
You can change that also in the m1 poms. If there're already releases
we can relocate the to the new groupid, so people using the old one
will get a warning althoug still working.
On 2/27/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Alex Karasulu wrote:
> > Hiya,
> >
> > The directory project
Dennis Lundberg wrote:
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact this list and make sure
the deployed pom is correct. It is
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact this list and make sure the
deployed pom is correct. It is located here:
http://tes
Alex Karasulu wrote:
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact this list and make sure
the deployed pom is correct. It is located here:
http://te
Hiya,
The directory project depends on commons-daemon 1.0.1 and we had to
update the maven2 repo with a temporary pom.xml to allow our recent
release to go through. I wanted to contact this list and make sure the
deployed pom is correct. It is located here:
http://test.maven.codehaus.org/m
17 matches
Mail list logo
