Hi all, as for Proximity, i can only repeat my previous statement: Px currently logs every request (done by Px-webapp frontent servlet).
My huntch is that you did not configure maven properly to use proximity as snapshot repos. Per default, maven does not have snapshot repo (as far as i know...). It could be a little awkward, but you should direct maven to proximity twice: once as central mirror and once as snapshot repo for your inhouse snapshots. There is no contradiction in this "little trick", since your px-published-inhouse repo contains your own snapshots (px will not find them on any remote peer) -- these repos ARE disjunct, no? ~t~ On 6/5/06, ben short <[EMAIL PROTECTED]> wrote:
Tamás, There are logs, and I can see requests for the released version of the artifact im after, but nothing for the snapshot requests. I have tried the -U flag also. I havent tried what Olivier suggested yet, will try it tomorrow. Ben On 6/5/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > I'm not using proximity but Maven proxy at the moment. > > On 6/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Same here...one thing I think I did that seemed to work was to throw the > > -U cmd on the compile, ie. "mvn -U compile". Try that and let us know > > if it works. > > > > --Rudy > > > > -----Original Message----- > > From: Paul Spencer [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 05, 2006 10:29 AM > > To: Maven Users List > > Subject: Re: [M2] Snapshots deployed to server not being found > > > > Ben, > > I have seen the same behavior. Although I have not had time to > > determine what is > > the root cause, I think it may the IDE, Eclipse in my case, locking the > > dependency > > in the local repository and Maven not complaining when it can not > > replace the file. Again > > I have not had time to verify this, it is just a hunch. > > > > Paul Spencer > > > > ben short wrote: > > > Hi, > > > > > > I am trying to include a snapshot that has been deployed to our > > > internal repository. When I do mvn compile, maven complains that it > > > couldn't resolve the dependency. > > > > > > Is this a bug with maven 2.0.4? > > > > > > Ben > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
