Just for clearity, that should be done through the dependencyManagament section. depMgmt impacts transitive deps as well.
/Anders On Wed, Apr 28, 2010 at 04:08, Justin Edelson <justinedel...@gmail.com>wrote: > Perhaps it is defined in a parent pom. > > In any case, you can fix this easily by setting the version in your pom. > > Justin > > On Apr 27, 2010, at 8:59 PM, Grant Birchmeier <gbirchme...@connamara.com> > wrote: > > > I can't find where the range is specified. My output says: > > > > --- > > Path to dependency: > > 1) com.connamara.ontrade:simplespreader:jar:1.0 > > 2) org.marketcetera:ors:jar:1.6.0 > > --- > > > > But neither pom specifies a version for log4j. I'm not even sure why > > it looking for 1.2.13 as opposed to something later. I see that the > > file you linked was last updated March 31, which probably explains why > > this trouble just started, as we last did a build prior to that. > > > > I got it to build by hacking my > > ~/.m2/repository/log4j/log4j/maven-metadata-central.xml to include > > 1.2.13. > > > > This is not really an optimal solution, as every user will need to do > > this. Is there a better way? > > > > (Our software uses third-party components with their own poms. Until > > now, we haven't had any trouble with the Maven part. Clearly, though, > > I'm still kind of new to this.) > > > > -Grant > > > > > > On Tue, Apr 27, 2010 at 7:26 PM, Justin Edelson <justinedel...@gmail.com> > wrote: > >> Because you're using a range, which requires better metadata than log4j > >> has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml > >> > >> On 4/27/10 8:21 PM, Grant Birchmeier wrote: > >>> If anyone can help, I'd appreciate it. This is driving me up the > >>> wall. I tried googling, but I couldn't find what I needed. > >>> > >>> When I build, I get this error: > >>> > >>> --- > >>> Couldn't find a version in [1.2.15, 1.2.16] to match range > [1.2.13,1.2.13] > >>> log4j:log4j:jar:null > >>> --- > >>> > >>> But when I list the contents of my repo dir, I clearly have a "1.2.13" > version: > >>> > >>> --- > >>> 1143 ~/$ ls ~/.m2/repository/log4j/log4j/ > >>> 1.2.13/ > >>> 1.2.14/ > >>> 1.2.15/ > >>> maven-metadata-central.xml > >>> [...etc...] > >>> --- > >>> > >>> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14 > >>> and 1.2.15? > >>> > >>> Thanks to anyone who can help > >>> > >>> -Grant > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: users-h...@maven.apache.org > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
