On Thu, Sep 11, 2008 at 2:08 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Thu, Sep 11, 2008 at 10:14 AM, Yaakov Chaikin > <[EMAIL PROTECTED]> wrote: > >> My project has a need to use a custom maven2 repository. I have setup >> a directory to be exposed through our web server. Our server is only >> accessible through HTTPS (with a valid certificate) and a >> username/password had to be setup as well. One of my other >> requirements was not to allow maven to download from a publicly >> available repository (not even the plugins), but only go to our own >> server. The repository itself is browseable, so I know that works just >> fine. However, maven can't seem anything and fails right away with >> this: > > Try it with -U on the command line to force it to check again. The > default update policy is once per day and it may have cached an error > from earlier today.
Just tried it: 'mvn -U clean' Same thing. Any other ideas? > To prevent access to outside repositories, overriding 'central' isn't > enough. You'll also need to use mirrors in your settings, > specifically mirrorOf=* to catch any extras that show up. > > http://maven.apache.org/guides/mini/guide-mirror-settings.html Thanks. I'll keep this in mind once the previous issue is resolved. Yaakov. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
