I'm actually thinking it's some kind of server read timeout, either on their end or my end. It doesn't seem to have a reason. Anyway, yes having the poms fixes the problem. It will be useful to have them generated once 2.0.1 comes out, which according to another post seem like it may be the next couple of weeks. I read that they are targeting a release for ApacheCon, which is mid December...
-----Original Message----- From: Anuerin Diaz [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 9:04 AM To: Maven Users List Subject: Re: [m2] I need clarification on repositories On 12/2/05, Frank Russo <[EMAIL PROTECTED]> wrote: > I'm not sure what you mean by pom.xml in this context. That is for my project, which I included in my email. Do you mean the .pom file for the jar? If that's the case, the option to create you talk about won't be available until 2.0.1. I checked it on the jira site. It is fixed. I forget the exact number. > yeah, my mistake. there shouldn't be a ".xml" on the "pom". and i also create my own library poms. > That was basically the problem, which answers my number 3 below. Yes, each jar has to have a .pom in the local repository. However, this wasn't always the case. I had 27 jars that I loaded into my local repository, none of which had poms. Usually, everything worked fine. It would always look in central since the pom was missing, but if it didn't find it, then it would ignore it. But sometimes I'd get that intermittent problem where it would fail. Not sure why. I have added poms for each jar, and now it never looks in central, except for the daily checked I've configured. > i think that pom checking is done when maven wants to check for updated versions of the library. the first few times might be ok but once it tries to verify and it does not see a library pom then it assumes that it could find it from the official repositories. this are all our assumptions and i have not yet had the opportunity of getting hold of a document that explains this cycle. we just made it a policy to make sure that those pom files are present to minimize the headache. it seems to be working because we have a dozen jar files manually added in the project repository and we are not encountering this issue. :) <snip> ciao! -- "Programming, an artform that fights back" Anuerin G. Diaz Registered Linux User #246176 Friendly Linux Board @ http://mandrivausers.org/index.php http://capsule.ramfree17.org , when you absolutely have nothing else better to do --------------------------------------------------------------------- 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]
