Maven Upload Requests

Carlos Sanchez added a comment - 24/Mar/09 6:18 AM You can create a synced repo in svn, like com.google.code.findbugs https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv

Jose M Beas added a comment - 24/Mar/09 7:07 AM Mmm, I've been having a look at http://code.google.com/p/findbugs but I'm not sure if this is a good reference because there is no pom.xml in their trunk or any of their tags. Apparently they're using ant to build the project. Anyway, I have a couple of doubts in case I use the following csv line to rsync. "org.concordion","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Jose M Beas","jose.m.beas@gmail.com",,"http://concordion.googlecode.com/svn/repos/release-repository/" 1) I have mimicked the second column although it has no meaning to me (I have to admit that I don't really understand how the rsync thing works) 2) I have guessed the last column is where I make my deployments but I'm not sure if I can deploy using svn as a protocol (apparently Findbugs is not doing that in this way because there is no reference either in the non-existing pom.xml or in http://code.google.com/p/findbugs/source/browse/repos/release-repository/com/google/code/findbugs/findbugs/1.3.7/findbugs-1.3.7.pom) I have not made any change yet in our source code because I would prefer to have this bundled release asap and then I can start working in a new rsync'd release. Would it be possible, please?

Jose M Beas added a comment - 24/Mar/09 8:43 AM I've been doing some tries and need to clarify a couple of things more: 3) Do we need a hosted repository to deploy our artifacts? (Then the second column in the csv line makes sense to me) 4) What should I put in the distributionManagement section in my pom.xml in order to deploy in https://concordion.googlecode.com/svn/repos/releases? I have tried svn:https://concordion.googlecode.com/svn/repos/releases but "mvn deploy" finishes with an "Unssuported protocol" error. Thanks, JMB

Jose M Beas added a comment - 24/Mar/09 9:35 AM Well, I must apologize. I've finally found the way to make the deployment using Maven. The trick consists in: a) using Maven 2.0.9 (the embedder was apparently not working) b) using dav:https://concordion.googlecode.com/svn/repos/releases in the distributionManagement section c) including the username and password in settings.xml My distributionManagement is now:     <distributionManagement>      <repository>      <id>concordion-releases</id>      <uniqueVersion>false</uniqueVersion>      <url>dav:https://concordion.googlecode.com/svn/repos/releases&lt;/url>      </repository>      <snapshotRepository>      <id>concordion-snapshots</id>      <uniqueVersion>true</uniqueVersion>      <url>dav:https://concordion.googlecode.com/svn/repos/snapshots&lt;/url>      </snapshotRepository>     </distributionManagement> And in my settings.xml: <settings> <servers> <server> <id>concordion-releases</id> <username>myusername</username> <password>xyxyxyxyxyx</password> </server> </servers> </settings> I still have to polish an issue regarding an assembly and asap I'll provide you with the csv line to sync.

Jose M Beas added a comment - 24/Mar/09 11:25 AM "org.concordion","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Jose M Beas","jose.m.beas@gmail.com",,"http://concordion.googlecode.com/svn/repos/releases/" Please upload with sync. Thanks JMB