commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@apache.org>
Subject Re: [daemon] Deploying maven 2 pom for release 1.0.1
Date Mon, 27 Feb 2006 20:39:42 GMT
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 <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>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
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