I use HTTP for ordinary development. However file is also used often in tooling. For example I have a custom release plugin that deploys to a file based staging repository. Only when the release completely succeeds, is the staging repository uploaded (using the staging plugin) to the real repository. This buys me atomic releases (because release:perform does fail sometimes even if release:prepare didn't).
On Wed, May 21, 2008 at 8:15 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > Hi, > > I'm just trying to get some data on what protocol is used to retrieve > artifacts. This question strictly relates to what you use for retrieval. > Most people I have seen use a web server or a shared network drive, but I'd > like to get some feedback. > > [ ] Our team uses HTTP to retrieve our artifacts > [ ] Our team intends to use HTTP to retrieve our artifacts > [ ] Our team uses the filesystem > [ ] Our team does not use HTTP or the filesystem because .... please say > what protocol you use and the reason > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > A language that doesn't affect the way you think about programming is not > worth knowing. > > — Alan Perlis > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
