I think you may be barking up the wrong tree here. The m2eclipse plugin ships with its own snapshot of the versions available in the public repository. It does not go out to the repositories in real time to support the "Add Dependency" feature. See the m2eclipse documentation for more information.
Pete -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Sunday, January 13, 2008 11:47 PM To: Maven Users List Subject: Re: Newbie: libraries out of date in repository On Jan 13, 2008 8:31 PM, Chris <[EMAIL PROTECTED]> wrote: > Thanks. I'm finding that quite few of the libraries I need are out of > date or incomplete (or scattered in several different places and > completely disorganized). > > How, in general, can I solve this problem without being dependent on the > dev team for each library? > > Can I create my own repository someplace on our internal network so that > all our developers at my company can point at a clean, well-organized > common repository? Or can I alter the main maven repository somehow? While it's more trouble up front, working with the project developers to get the libraries into the central repo is the best thing for the community. If the project developers aren't interested, you can submit things for upload [1]. In addition to that, it's a very good idea to establish your own internal repositories. One of the repository managers such as Archiva, Proximity or Artifactory can be very useful here, especially if you want to proxy the various remote repos you're using. [1] http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- Wendy --------------------------------------------------------------------- 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]
