You should use Maven-proxy and an internal repository wich share the same location. This way, your goal is going to be achieved automatically.
Or if you prefer a manual process, just run regularly a synchronise file tool between Maven-Proxy repository and your internal repository. On 3/11/06, Khin, Gerald <[EMAIL PROTECTED]> wrote: > > On 3/10/06, Treloar, Barrie <[EMAIL PROTECTED]> wrote: > > On 3/10/06, Khin, Gerald <[EMAIL PROTECTED]> wrote: > > > Hi! > > > > > > Being a newbie to maven, I wonder if this idea could work: > > > > [del] > > > > The first question that springs to mind is Why? > > > > What benefit is there to restrict maven in this way, it makes no sense. > > My idea behind is to conserve all things I needed to build my project so that > once my product will be released, that I will be still able to build my > project in case, even in a couple of years, completely independent of the > availability of the central repository and its public mirrors. > > > > > Control the version numbers of artifacts that you have sanctioned is > > a better way of enforcing standards in the organisation that banning > > maven from downloading more plugins. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
