I'm about to start working on this again in the maven user wiki, but there are a lot of questions to be asked.
1. Why are you doing this? It makes a lot of sense to do, but your reasons for doing it determine things later in the chain. 2. Where are you doing this? In a publicly accessible location, or internally, or both. 3. How do you want to do it? In it's simplest case, deployments into the public areas of a web server can be used as a repository, but that's not always the best way. There are a number of products that allow some forms of management for what are often called "3rd party repos", such as Proximity, Archiva, maven-proxy, etc. They work with varying degrees of effectiveness and difficulty in setup/maintenance On 12/8/06, Marc Boorshtein <[EMAIL PROTECTED]> wrote:
Hello All, I'm trying to understand how to create a 3rd party repository. I'm not looking to build a mirror of ibiblio, but instead have my own 3rd party repository in addition to the repository. Thanks Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways.
