You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2009/02/09 16:28:03 UTC
SSL on repository.zones.apache.org (was: Re: [vote] use repository.zones.apache.org
...)
Hi everyone,
I wanted to let everyone know that I've put together a _very_ small app
from some code I managed to swipe (looks like it's Oleg's style...if so,
thanks Oleg). The app works both via JNLP and command line, and installs
the self-signed certificate for repository.zones.apache.org into your
JDK's keystore. This should allow Maven to deploy to the repository when
you're using that JDK.
For some people, most notably Mac users, the ${java.home}/lib directory
is actually owned by root and is not group-writable, so you'll need to
use the command-line approach for the app, and prefix the command with
'sudo' to get root access for the execution.
More instructions can be found here:
http://repository.zones.apache.org/ssl
Thanks, and good luck. Let me know if you have any questions.
-john
Brian E. Fox wrote:
> As proposed in separate threads[1][2] and Infra jira[3], we have setup a
> new zone and repository manager for hosting Apache artifacts at
> https://repository.zones.apache.org. The service is now setup and
> several releases of Maven are already staged there.
>
>
>
> The initial idea was to use LDAP for committer auth/authz, but it isn't
> ready yet. In the meantime, a new security realm has been created and
> all Apache committers can log in to the system using their credentials.
> As each project comes over, we will use the existing svn group mappings
> to port the users into the correct group.
>
>
>
> To complete the process of using this for Maven artifacts, the following
> needs to be done:
>
> 1) Configure the new location as a sync source to Central.
>
> 2) Map the rest of the Maven PMC and committer accounts into the
> Maven Group
>
> 3) Move the artifacts from People.apache.org for org/apache/maven/*
> over to the hosted repository
>
> 4) Update documentation on how to release, stage and promote
>
> 5) Adjust the Parent pom to use the new urls for distribution
> management for both snapshots and releases
>
> 6) Release parent poms, update snapshots etc.
>
>
>
> For the time being, we can leave the snapshots in place at p.a.o and
> simply start deploying new versions to the zone. We can setup a proxy of
> the old snapshot and put this into a group with the new one and users
> can migrate over to the new snapshot url and eventually we can move the
> snapshots over.
>
>
>
> We are working with Apache Infra to get a machine neutral dns for this
> [4] and also an official https certificate[5] so hopefully those will
> happen shortly, specifically the dns before we update all the poms.
>
>
>
> The migration of this would happen project by project, with hopefully
> Maven leading the way.
>
>
>
> [1]
> http://www.nabble.com/-Proposal--Use-Nexus-to-actively-manage-the-Apache
> -repository-tt21759239.html#a21759239
>
> [2] Apache Infra list - I believe there are not public archives of this
>
> [3] https://issues.apache.org/jira/browse/INFRA-1885
>
> [4] https://issues.apache.org/jira/browse/INFRA-1890
>
> [5] https://issues.apache.org/jira/browse/INFRA-1891
>
>
>
> So lets vote:
>
> +1 Yes, lets lead the way at ASF with a better staging and releasing
> process
>
> +0 shrug
>
> -1 No, I like managing my artifacts by hand.
>
>
>
> ----------------------
>
> Brian Fox
>
> Apache Maven PMC
>
> http://blogs.sonatype.com/brian/
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: SSL on repository.zones.apache.org (was: Re: [vote] use repository.zones.apache.org ...)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Ok the new cert is in place.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Monday, February 09, 2009 11:18 AM
To: Maven Developers List
Subject: RE: SSL on repository.zones.apache.org (was: Re: [vote] use
repository.zones.apache.org ...)
Give me 2 hours to switch the cert to use the new dns which will be
https://repository.apache.org
-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org]
Sent: Monday, February 09, 2009 10:28 AM
To: Maven Developers List
Subject: SSL on repository.zones.apache.org (was: Re: [vote] use
repository.zones.apache.org ...)
Hi everyone,
I wanted to let everyone know that I've put together a _very_ small app
from some code I managed to swipe (looks like it's Oleg's style...if so,
thanks Oleg). The app works both via JNLP and command line, and installs
the self-signed certificate for repository.zones.apache.org into your
JDK's keystore. This should allow Maven to deploy to the repository when
you're using that JDK.
For some people, most notably Mac users, the ${java.home}/lib directory
is actually owned by root and is not group-writable, so you'll need to
use the command-line approach for the app, and prefix the command with
'sudo' to get root access for the execution.
More instructions can be found here:
http://repository.zones.apache.org/ssl
Thanks, and good luck. Let me know if you have any questions.
-john
Brian E. Fox wrote:
> As proposed in separate threads[1][2] and Infra jira[3], we have setup
a
> new zone and repository manager for hosting Apache artifacts at
> https://repository.zones.apache.org. The service is now setup and
> several releases of Maven are already staged there.
>
>
>
> The initial idea was to use LDAP for committer auth/authz, but it
isn't
> ready yet. In the meantime, a new security realm has been created and
> all Apache committers can log in to the system using their
credentials.
> As each project comes over, we will use the existing svn group
mappings
> to port the users into the correct group.
>
>
>
> To complete the process of using this for Maven artifacts, the
following
> needs to be done:
>
> 1) Configure the new location as a sync source to Central.
>
> 2) Map the rest of the Maven PMC and committer accounts into the
> Maven Group
>
> 3) Move the artifacts from People.apache.org for
org/apache/maven/*
> over to the hosted repository
>
> 4) Update documentation on how to release, stage and promote
>
> 5) Adjust the Parent pom to use the new urls for distribution
> management for both snapshots and releases
>
> 6) Release parent poms, update snapshots etc.
>
>
>
> For the time being, we can leave the snapshots in place at p.a.o and
> simply start deploying new versions to the zone. We can setup a proxy
of
> the old snapshot and put this into a group with the new one and users
> can migrate over to the new snapshot url and eventually we can move
the
> snapshots over.
>
>
>
> We are working with Apache Infra to get a machine neutral dns for this
> [4] and also an official https certificate[5] so hopefully those will
> happen shortly, specifically the dns before we update all the poms.
>
>
>
> The migration of this would happen project by project, with hopefully
> Maven leading the way.
>
>
>
> [1]
>
http://www.nabble.com/-Proposal--Use-Nexus-to-actively-manage-the-Apache
> -repository-tt21759239.html#a21759239
>
> [2] Apache Infra list - I believe there are not public archives of
this
>
> [3] https://issues.apache.org/jira/browse/INFRA-1885
>
> [4] https://issues.apache.org/jira/browse/INFRA-1890
>
> [5] https://issues.apache.org/jira/browse/INFRA-1891
>
>
>
> So lets vote:
>
> +1 Yes, lets lead the way at ASF with a better staging and releasing
> process
>
> +0 shrug
>
> -1 No, I like managing my artifacts by hand.
>
>
>
> ----------------------
>
> Brian Fox
>
> Apache Maven PMC
>
> http://blogs.sonatype.com/brian/
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: SSL on repository.zones.apache.org (was: Re: [vote] use repository.zones.apache.org ...)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Give me 2 hours to switch the cert to use the new dns which will be
https://repository.apache.org
-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org]
Sent: Monday, February 09, 2009 10:28 AM
To: Maven Developers List
Subject: SSL on repository.zones.apache.org (was: Re: [vote] use
repository.zones.apache.org ...)
Hi everyone,
I wanted to let everyone know that I've put together a _very_ small app
from some code I managed to swipe (looks like it's Oleg's style...if so,
thanks Oleg). The app works both via JNLP and command line, and installs
the self-signed certificate for repository.zones.apache.org into your
JDK's keystore. This should allow Maven to deploy to the repository when
you're using that JDK.
For some people, most notably Mac users, the ${java.home}/lib directory
is actually owned by root and is not group-writable, so you'll need to
use the command-line approach for the app, and prefix the command with
'sudo' to get root access for the execution.
More instructions can be found here:
http://repository.zones.apache.org/ssl
Thanks, and good luck. Let me know if you have any questions.
-john
Brian E. Fox wrote:
> As proposed in separate threads[1][2] and Infra jira[3], we have setup
a
> new zone and repository manager for hosting Apache artifacts at
> https://repository.zones.apache.org. The service is now setup and
> several releases of Maven are already staged there.
>
>
>
> The initial idea was to use LDAP for committer auth/authz, but it
isn't
> ready yet. In the meantime, a new security realm has been created and
> all Apache committers can log in to the system using their
credentials.
> As each project comes over, we will use the existing svn group
mappings
> to port the users into the correct group.
>
>
>
> To complete the process of using this for Maven artifacts, the
following
> needs to be done:
>
> 1) Configure the new location as a sync source to Central.
>
> 2) Map the rest of the Maven PMC and committer accounts into the
> Maven Group
>
> 3) Move the artifacts from People.apache.org for
org/apache/maven/*
> over to the hosted repository
>
> 4) Update documentation on how to release, stage and promote
>
> 5) Adjust the Parent pom to use the new urls for distribution
> management for both snapshots and releases
>
> 6) Release parent poms, update snapshots etc.
>
>
>
> For the time being, we can leave the snapshots in place at p.a.o and
> simply start deploying new versions to the zone. We can setup a proxy
of
> the old snapshot and put this into a group with the new one and users
> can migrate over to the new snapshot url and eventually we can move
the
> snapshots over.
>
>
>
> We are working with Apache Infra to get a machine neutral dns for this
> [4] and also an official https certificate[5] so hopefully those will
> happen shortly, specifically the dns before we update all the poms.
>
>
>
> The migration of this would happen project by project, with hopefully
> Maven leading the way.
>
>
>
> [1]
>
http://www.nabble.com/-Proposal--Use-Nexus-to-actively-manage-the-Apache
> -repository-tt21759239.html#a21759239
>
> [2] Apache Infra list - I believe there are not public archives of
this
>
> [3] https://issues.apache.org/jira/browse/INFRA-1885
>
> [4] https://issues.apache.org/jira/browse/INFRA-1890
>
> [5] https://issues.apache.org/jira/browse/INFRA-1891
>
>
>
> So lets vote:
>
> +1 Yes, lets lead the way at ASF with a better staging and releasing
> process
>
> +0 shrug
>
> -1 No, I like managing my artifacts by hand.
>
>
>
> ----------------------
>
> Brian Fox
>
> Apache Maven PMC
>
> http://blogs.sonatype.com/brian/
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org