This is an automated email from the ASF dual-hosted git repository. martin_s pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/archiva-redback-components-spring-taskqueue.git
commit 7654ac19260f2584c55a567d4508796556314f83 Author: Olivier Lamy <[email protected]> AuthorDate: Fri Apr 6 22:40:56 2012 +0000 fix pom due to asf move git-svn-id: https://svn.apache.org/repos/asf/archiva/redback/redback-components/trunk@1310624 13f79535-47bb-0310-9956-ffa450edef68 --- pom.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pom.xml b/pom.xml index 3808edf..b93dff4 100644 --- a/pom.xml +++ b/pom.xml @@ -27,21 +27,21 @@ <modelVersion>4.0.0</modelVersion> <artifactId>spring-taskqueue</artifactId> <name>Spring Task Queue</name> - <version>1.1-SNAPSHOT</version> + <version>2.0-SNAPSHOT</version> - <url>http://redback.codehaus.org/components/${project.artifactId}</url> + <url>http://archiva.apache.org/redback/components/${project.artifactId}</url> <distributionManagement> <site> - <id>codehaus.org</id> - <url>dav:https://dav.codehaus.org/redback/components/${project.artifactId}</url> + <id>apache.website</id> + <url>scp://people.apache.org/www/archiva.apache.org/redback/components/${project.artifactId}</url> </site> </distributionManagement> <scm> - <connection>scm:svn:https://svn.codehaus.org/redback/components/trunk/spring-taskqueue</connection> - <developerConnection>scm:svn:https://svn.codehaus.org/redback/components/trunk/spring-taskqueue</developerConnection> - <url>http://fisheye.codehaus.org/browse/redback/components/trunk/spring-taskqueue</url> + <connection>scm:svn:http://svn.apache.org/repos/asf/archiva/redback/redback-components/trunk/spring-taskqueue/</connection> + <developerConnection>scm:svn:https://svn.apache.org/repos/asf/archiva/redback/redback-components/trunk/spring-taskqueue/</developerConnection> + <url>http://svn.apache.org/viewvc/archiva/redback/redback-components/trunk/spring-taskqueue/</url> </scm> <dependencies> -- To stop receiving notification emails like this one, please contact [email protected].
