When you installed those dependencies in your local repo, did you use -DgeneratePom=true ?
If not, reinstall the 3rd party artifacts and use that parameter so poms are created, to avoid this "downloading poms from central" thing in the future. Wayne On 5/8/06, Tim McCune <[EMAIL PROTECTED]> wrote:
Newbie alert: I've only been seriously trying out Maven 2 for a couple days now. Here's my biggest headache so far. Every time I build, I have to sit and wait while Maven tries to download poms from the central repository for all of the jars that have no corresponding poms. I get a bunch of messages like: Downloading: http://repo1.maven.org/maven2/jboss/jboss-ejb3x/rc5/jboss-ejb3x-rc5.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Sure, in a perfect world, every jar would have a corresponding pom, but come on. There are always going to be jars without poms, and this shouldn't stop me from using them. It seems like Maven should make a single attempt to grab a pom when it downloads the jar, realize that there isn't one, make a note of it in the local repository, and use that information in the future so it doesn't keep making futile attempts to download the pom. Am I understanding the problem correctly? Any suggestions for a fix? Thanks. --Tim --------------------------------------------------------------------- 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]
