Hi, At the moment HTTP/REST is the primary protocol and we do not have any concerete plans to support additional protocols (though we do not rule it out). It can be worked around by using the Artifactory Hudson plugin (if you build with Hudson) or by using the default lightweight HTTP wagon.
Thanks, Yoav On Mon, Jan 11, 2010 at 9:49 AM, Magnus Grimsell < magnus.grims...@idainfront.se> wrote: > Hi Noam, > > > > Thanks for your help! > > The fact that Maven uploads the artifacts twice also explains why it takes > so much longer to deploy with web dav. > > Before moving to artifactory we used scp which was much faster. > > Are there any plan to support other wagons like ftp or scp? > > > > /Magnus > > > > *Från:* Noam Y. Tenne [mailto:no...@jfrog.org] > *Skickat:* den 10 januari 2010 18:32 > > *Till:* artifactory-users@lists.sourceforge.net > *Ämne:* [Disarmed] Re: [Artifactory-users] [Disarmed] Re: [Disarmed] Re: > [Disarmed] Re: [Disarmed] Re: [Disarmed] Re: cant deploy large artifacts > > > > Hi > > >From some debugging and digging around, it seems like the trouble you're > experiencing originates in the wagon. > It's known that when using credentials for deployment, maven first attempts > to deploy with anonymous, and will provide credentials only if challenged > for them. > It also looks like no caching is done for successful challenges, so each > request doubles. > The problem is that this double requesting can cause problems (corruption > of data, timeouts and more). > I managed to reproduce your problem using a specific deployment user via > DAV. > To my understanding you can fix this behavior by enabling preemptive > authentication, but it looks like there are still some issues with it: > > http://jira.codehaus.org/browse/MNG-4301 > http://jira.codehaus.org/browse/WAGON-277 > > For the sake of the test, I tried the same scenario, only using anonymous > as a deployer (which prevents the double requests), and the deployment > succeeded. > I also managed to deploy via HTTP, but as you mentioned, this method has > it's memory issues, and I had to preserve configure huge amounts of memory > for it. > > HTH > Noam > > Magnus Grimsell wrote: > > It seems I was a little bit too fast to judge. > > After the deploy command crash, artifactory hangs when browsing the > repository. No errors in the logs. > > When restarting the server I get the message: > > 2010-01-08 14:18:59,353 [main] [WARN ] (o.a.j.c.u.RepositoryLock:134) - > Existing lock file /home/artifactory/repo-data/data/.lock detected. > Repository was not shut down properly. > > > > > > *Från:* Magnus Grimsell > [mailto:magnus.grims...@idainfront.se<magnus.grims...@idainfront.se>] > > *Skickat:* den 8 januari 2010 13:44 > *Till:* artifactory-users@lists.sourceforge.net > *Ämne:* [Disarmed] Re: [Artifactory-users] [Disarmed] Re: [Disarmed] Re: > [Disarmed] Re: [Disarmed] Re: cant deploy large artifacts > > > > 2.1.3 seems to work a little bit better. I still cannot deploy large > artifacts with Maven 2.2.1. However I dont get a ”read timeout” but a > ”socket write error”. > > And there is no lock problem anymore. > > > > Thanks > > Magnus > > > > [INFO] > ------------------------------------------------------------------------ > > [ERROR] BUILD ERROR > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Error deploying artifact: Software caused connection abort: socket > write error > > > > [INFO] > ------------------------------------------------------------------------ > > [INFO] For more information, run Maven with the -e switch > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Total time: 4 minutes 7 seconds > > [INFO] Finished at: Fri Jan 08 13:01:51 CET 2010 > > [INFO] Final Memory: 22M/39M > > [INFO] > ------------------------------------------------------------------------ > > > > *Från:* Noam Y. Tenne [mailto:no...@jfrog.org <no...@jfrog.org>] > *Skickat:* den 7 januari 2010 17:22 > *Till:* artifactory-users@lists.sourceforge.net > *Ämne:* [Disarmed] Re: [Artifactory-users] [Disarmed] Re: [Disarmed] Re: > [Disarmed] Re: cant deploy large artifacts > > > > I'll look into 2.2.1 and see if I can find anything, thanks for the info. > Meanwhile, we released a new version (2.1.3) that also solved some problems > we had with locking exceptions. Could you please upgrade and check if the > problem persists? > > Thanks > Noam > > Magnus Grimsell wrote: > > Hi Noam, > > > > Now I have had the time to do some more testing. > > It seems I can only reproduce this issue with Maven 2.2.1. > > With Maven 2.0.9 and 2.0.10 everything works fine. > > >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Artifactory-users mailing list Artifactory-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/artifactory-users
