Hi Alex, Actually, I faced the same situation the last time I wanted to release Studio (version 1.4.0).
No need to downgrade to ASF wide version 4 pom. You can use the version 5 and override the 'release.altDeploymentRepository' property by this one in your settings.xml file: <release.altDeploymentRepository>-DaltDeploymentRepository=apache.release::default::scpexe:// people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository </release.altDeploymentRepository> This will force the deployment on the old repository on people.apache.org. Regards, Pierre-Arnaud On Mon, Aug 17, 2009 at 1:23 AM, Alex Karasulu <[email protected]> wrote: > Hi all, > > For our project pom. I am reverting back to using the ASF wide version 4 > pom. Version 5 removed the old repositories where ssh access to people . > apache.org was used to deploy releases. This supposedly is outdated > although still active. > > A new repository using this Nexus server is running on > repository.apache.org. Instead of using ssh to upload releases this > server uses webdav and has some kind of feature for publishing and releasing > deployments with staging. To use this we'll have to vote on it and then ask > the maven folks to give us access to this Nexus server. That will take time > though so for this release I'll use the old way of ssh pushing the release > to people.apache.org. > > For more reading on this matter consult the following JIRA issue and > documentation: > > ---- > [0] - https://issues.apache.org/jira/browse/INFRA-1896 > [1] - http://www.apache.org/dev/repository-faq.html > > Cheers! > -- > Alex Karasulu > My Blog :: http://www.jroller.com/akarasulu/ > Apache Directory Server :: http://directory.apache.org > Apache MINA :: http://mina.apache.org > >
