My understanding of the plan is that this will replace the repo at people.apache.org. It would be synched to Maven central. There was some discussion about this on infra last week and also on the maven developers list.

Ralph

On Feb 8, 2009, at 11:55 AM, Henri Yandell wrote:

What does that mean? We would upload to their directly rather than the
ASF sync repo?

On Sat, Feb 7, 2009 at 1:08 PM, Ralph Goers <ralph.go...@dslextreme.com > wrote:
Actually, the maven folks (of which I am one) are creating a new Nexus repo at https://repository.zones.apache.org. I would suggest we focus on using
that in the future.

Ralph

On Feb 7, 2009, at 12:59 PM, Niall Pemberton wrote:

On Wed, Feb 4, 2009 at 6:49 AM, Oliver Heger
<oliver.he...@oliver-heger.de> wrote:

According to a post on the user list the latest release of
[configuration]
(1.6) did not make it into the maven 2 repository.

When doing the release I copied the jars and the pom into the Java
repository at [1] as described in section 8 of [2]. This used to work for the older releases. Is there something more required to get the artifacts
deployed to the central maven 2 repository?

I thought configuration 1.6 was an m2 release - if it was then
probably should have been deployed to the pao m2 repo instead:

http://people.apache.org/repo/m2-ibiblio-rsync-repository/

Even then though you still need to ping repository@ for the first m2
release since they have to add the group to be synced

Niall

Thanks
Oliver

[1] /www/people.apache.org/repo/m1-ibiblio-rsync-repository
[2] http://commons.apache.org/releases/release.html

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



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



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



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



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

Reply via email to