commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <>
Subject Re: [daemon] Deploying maven 2 pom for release 1.0.1
Date Fri, 03 Mar 2006 20:38:36 GMT
Henri Yandell wrote:
> On 2/27/06, 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 located here:
>>> Also I'd like to make sure we can get m2 deployments working for commons
>>> daemon from now on.  I'm a committer but I wanted to ask if it's ok to
>>> add a m2 pom alongside the m1 project.xml so we can update the m2
>>> repository.
>> If we start to add m2 poms to SVN I do think we should use the Maven 2
>> way to declare groupId, like this:
>>    <groupId>org.apache.commons</groupId>
>>    <artifactId>commons-daemon</artifactId>
> I think it should be:   org.apache.jakarta.commons
> It's not the package, just a grouping, so let's get it right at the
> ASF this time.

This page [1] says to use the package, but I have taken this question 
over to [2] to get this clarified. Will post the 
result back here later.



Dennis Lundberg

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message