commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <aok...@bellsouth.net>
Subject Re: [daemon] Deploying maven 2 pom for release 1.0.1
Date Fri, 03 Mar 2006 13:47:22 GMT
Henri Yandell wrote:
> On 2/27/06, Dennis Lundberg <dennisl@apache.org> 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:
>>>
>>> http://test.maven.codehaus.org/maven2/commons-daemon/commons-daemon/1.0.1/
>>>
>>> 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.
>
> [I'm suggesting stuff on repostitory@apache that would force us to do
> this btw :), we wouldn't have write permissions to org.apache.commons]
>   
I thought that was the best way to go.  I should have spoken up.  But I 
agree this is best to do from the onset. 

Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message