Hi, please read this email I sent and see if it fixes the problem for you guys:
https://groups.google.com/group/google-code-hosting/browse_thread/thread/8d3ea9e7f342f9e1 On Wed, Mar 17, 2010 at 4:49 AM, altumano <[email protected]> wrote: > Same problem here. > I tried to force maven to use wagon-maven-plugin 1.0-beta-1 and 1.0- > beta-3 (by adding them as build plugin) but it did not help. > > > On Mar 16, 5:06 pm, wohlgemuth <[email protected]> wrote: >> nope still working on it and have it failing on like 8 projects so far. >> Right now I install to my local repository, than copy the files to a >> checkout of my maven repository and than committing it. t's slightly >> frustrating at least and now I'm writing shell scripts again. >> >> an example config which worked forever would be: >> >> <build> >> <extensions> >> <extension> >> <groupId>org.jvnet.wagon-svn</groupId> >> <artifactId>wagon-svn</artifactId> >> <version>1.9</version> >> </extension> >> </extensions> >> </build> >> >> <distributionManagement> >> <repository> >> <uniqueVersion>false</uniqueVersion> >> <id>googlecode</id> >> >> <url>svn:https://binbase-maven.googlecode.com/svn/trunk/repo</url> >> </repository> >> <snapshotRepository> >> <uniqueVersion>false</uniqueVersion> >> <id>googlecode</id> >> >> <url>svn:https://binbase-maven.googlecode.com/svn/trunk/repo</url> >> </snapshotRepository> >> </distributionManagement> >> >> now the interresting quesiton is, my logfile shows: >> >> [INFO] binbase-create-database >> [INFO] binbase-updater >> [INFO] examples >> [INFO] taverna >> WAGON_VERSION: 1.0-beta-2 >> [INFO] snapshot >> org.codehaus.mojo:jboss-packaging-maven-plugin:2.0-SNAPSHOT: checking >> for updates from codehaus >> [INFO] snapshot >> org.codehaus.mojo:jboss-packaging-maven-plugin:2.0-SNAPSHOT: checking >> for updates from codehaus-snapshot >> [INFO] snapshot >> org.codehaus.mojo:jboss-packaging-maven-plugin:2.0-SNAPSHOT: checking >> for updates from repo1 >> >> which indicates it's using wagon version 1.0-beta-2 for some reason, >> which might have a bug. Now why the hell is maven jumping to >> 1.0-beta-2 without me telling it to or me changing anything in >> configuration. Sadly I don't have any old logfiles to see if they are >> also printing out WAGON_VERSION: 1.0-beta-2 or if they are printing >> out the correct version. >> >> So any ideas? >> >> On Tue, Mar 16, 2010 at 2:52 AM, Harald Pehl <[email protected]> >> wrote: >> > Hi, >> >> > I'm running into the same problems when trying to do "mvn deploy" to >> > my google code repository using the wagon-svn extension. >> >> > Did you find a solution for this? >> >> > Harald >> >> > On 15 Mrz., 15:30, wohlgemuth <[email protected]> wrote: >> >> hi, >> >> >> I will setup an example how to reproduce it later today. Thanks for your >> >> help! >> >> >> g. >> >> >> On Mon, Mar 15, 2010 at 6:47 AM, Ben Collins-Sussman <[email protected]> >> >> wrote: >> >> > How about doing an HTTP network trace and capturing all the HTTP >> >> > requests/responses? Then we might have a clue about what's going >> >> > wrong. >> >> >> > Either that, or you need to give us an exact series of steps for >> >> > reproducing the problem. >> >> >> > On Sun, Mar 14, 2010 at 9:00 PM, wohlgemuth <[email protected]> >> >> > wrote: >> >> >> the thin is I'm using the svn wagon in the same version since over a >> >> >> year, so nothing changed in this software which would cause a problem. >> >> >> I basically always get a 'can't close connection' issue. And there >> >> >> shows nothing up in the log. >> >> >> >> g. >> >> >> >> On Sat, Mar 13, 2010 at 5:41 PM, Ben Collins-Sussman >> >> >> <[email protected]> wrote: >> >> >>> If regular svn updates and commits work, that makes me think there's >> >> >>> nothing wrong with the google svn server. I've never heard of >> >> >>> svn-wagon, but I'm guessing it's written around the 100% java svn >> >> >>> implementation "svnkit", which may have bugs of its own. Are you able >> >> >>> to do updates/commits using straight svnkit? >> >> >> >>> On Sat, Mar 13, 2010 at 5:46 PM, berlinguyinca >> >> >>> <[email protected]> wrote: >> >> >>>> hi, >> >> >> >>>> I'm using a google code project as maven repository for our >> >> >>>> opensource >> >> >>>> projects and to provide a mavenized access for other opensource >> >> >>>> project. >> >> >> >>>> For deployment we use the svn-wagon in version 1.8 or 1.9 and since a >> >> >>>> week or so I'm not longer able to deploy my artifacts. >> >> >> >>>> all what I get is: >> >> >> >>>> [INFO] Installing /Users/wohlgemuth/workspace/java/binbase/trunk/ >> >> >>>> binbase/binbase-core/uctask/uctask-xdoclet/target/uctask- >> >> >>>> xdoclet-3.4.2.jar to /Users/wohlgemuth/.m2/repository/edu/ucdavis/ >> >> >>>> genomics/metabolomics/binbase/binbase-core/uctask/uctask-xdoclet/3.4.2/ >> >> >>>> uctask-xdoclet-3.4.2.jar >> >> >>>> [INFO] [deploy:deploy] >> >> >>>> altDeploymentRepository = null >> >> >>>> Uploading: svn:https://binbase-maven.googlecode.com/svn/trunk/repo/ >> >> >>>> trunk/repo/edu/ucdavis/genomics/metabolomics/binbase/binbase-core/ >> >> >>>> uctask/uctask-xdoclet/3.4.2/uctask-xdoclet-3.4.2.jar >> >> >>>> [ERROR] Problem disconnecting from wagon - ignoring: Failed to close >> >> >>>> svn connection >> >> >>>> [INFO] Uploading project information for uctask-xdoclet 3.4.2 >> >> >> >>>> and the main problem seems to be: >> >> >> >>>> [ERROR] Problem disconnecting from wagon - ignoring: Failed to close >> >> >>>> svn connection >> >> >> >>>> I don't think it's related to the svn-wagon, since we use it for a >> >> >>>> long time and it only started recently. So I think it's somehow >> >> >>>> related to googe codes svn. We can do normal svn updates or commits >> >> >>>> without a problem. >> >> >> >>>> Anybody has an idea? This issue is breaking our complete build right >> >> >>>> now. >> >> >> >>>> thanks! >> >> >> >>>> -- >> >> >>>> You received this message because you are subscribed to the Google >> >> >>>> Groups "Project Hosting on Google Code" group. >> >> >>>> To post to this group, send email to >> >> >>>> [email protected]. >> >> >>>> To unsubscribe from this group, send email to >> >> >>>> [email protected]. >> >> >>>> For more options, visit this group >> >> >>>> athttp://groups.google.com/group/google-code-hosting?hl=en. >> >> >> >>> -- >> >> >>> You received this message because you are subscribed to the Google >> >> >>> Groups "Project Hosting on Google Code" group. >> >> >>> To post to this group, send email to >> >> >>> [email protected]. >> >> >>> To unsubscribe from this group, send email to >> >> >>> [email protected]. >> >> >>> For more options, visit this group >> >> >>> athttp://groups.google.com/group/google-code-hosting?hl=en. >> >> >> >> -- >> >> >> ------------------------------------------------------------ >> >> >> Lead Developer - Fiehnlab, UC Davis >> >> >> >> gert wohlgemuth >> >> >> [email protected] >> >> >> >> work: >> >> >>http://fiehnlab.ucdavis.edu/staff/wohlgemuth >> >> >> >> phone: >> >> >> (530) 383-0974 >> >> >> >> coding blog >> >> >>http://codingandmore.blogspot.com >> >> >> >> ------------------------------------------------------------ >> >> >> you're "a long time dead", as they say >> >> >> >> -- >> >> >> You received this message because you are subscribed to the Google >> >> >> Groups "Project Hosting on Google Code" group. >> >> >> To post to this group, send email to >> >> >> [email protected]. >> >> >> To unsubscribe from this group, send email to >> >> >> [email protected]. >> >> >> For more options, visit this group >> >> >> athttp://groups.google.com/group/google-code-hosting?hl=en. >> >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "Project Hosting on Google Code" group. >> >> > To post to this group, send email to >> >> > [email protected]. >> >> > To unsubscribe from this group, send email to >> >> > [email protected]. >> >> > For more options, visit this group >> >> > athttp://groups.google.com/group/google-code-hosting?hl=en. >> >> >> -- >> >> ------------------------------------------------------------ >> >> Lead Developer - Fiehnlab, UC Davis >> >> >> gert wohlgemuth >> >> [email protected] >> >> >> work:http://fiehnlab.ucdavis.edu/staff/wohlgemuth >> >> >> phone: >> >> (530) 383-0974 >> >> >> coding bloghttp://codingandmore.blogspot.com >> >> >> ------------------------------------------------------------ >> >> you're "a long time dead", as they say >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Project Hosting on Google Code" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://groups.google.com/group/google-code-hosting?hl=en. >> >> -- >> ------------------------------------------------------------ >> Lead Developer - Fiehnlab, UC Davis >> >> gert wohlgemuth >> [email protected] >> >> work:http://fiehnlab.ucdavis.edu/staff/wohlgemuth >> >> phone: >> (530) 383-0974 >> >> coding bloghttp://codingandmore.blogspot.com >> >> ------------------------------------------------------------ >> you're "a long time dead", as they say > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
