Andreas, just to get the terminology straight, there are really three broad categories of repository: * local * shared/enterprise * public
The term "local" in this context refers to a location on the developer/tool/client's own machine. I think you're using the word "local" to talk about shared repositories. The default Ivy settings that gets used if you don't specify one uses a combination of all three above, although the default shared one is a dummy repo since it just points to a local location. So really, for all practical purposes, you want to specify your own Ivy settings. For truly local Ivy repos, filesystem is the resolver/protocol that you will almost always use. For shared repos, there are all kinds of valid combinations. The most common I can think of: * filesystem (perhaps a Samba shared on NAS mount) * HTTP with SFTP for publishing (or even filesystem for publishing) * have Subversion double as your Ivy repo I believe there are teams who are using something like Artifactory or Nexus as their shared Ivy repository. On Mon, Dec 21, 2009 at 8:55 AM, Andreas Axelsson < [email protected]> wrote: > Is the file system the most common "repository" used for internal/private > Ivy modules, or is there some kind of Artifactory type system that one can > setup locally which works well with Ivy? Preferably in a Windows > environment. > > I read a lot about retrieving from Maven style repositories but little > about publishing to them. > > Cheers, > /Andreas Axelsson > >
