Who is asking for 1.2.13 now? I only see 1.2.15 in your poms?
I am not sure why you have the [] around the version in mmm's pom.xml
The [] means this version and no other. Any other version tag in
Maven merely indicates a preference for a version of a plugin or
dependency, which Maven will pay
I just needed to resolve this issue myself with log4j [1.2.13]. Working
example is below. Thank yous go out to the gentlemen pointing me to
depMgmt.
Case:
- Artifact mmm depends on log4j with version [1.2.13]
- Artifact nnn depends on mmm.
- Mvn clean install of nnn fails with Couldn't find a
Who is asking for 1.2.13 now? I only see 1.2.15 in your poms?
I am not sure why you have the [] around the version in mmm's pom.xml
Ron
On 16/05/2010 5:03 PM, Steve Francolla wrote:
I just needed to resolve this issue myself with log4j [1.2.13]. Working
example is below. Thank yous go out
Ohh, I'm sorry. Ugh. :-/
Below is the mmm pom that causes the install failure. This pom simulates
exactly how a project I'm depending on is erroneously defined. To get
around it, I've implemented the fix as in nnn.xml. Just providing a
concluding example here for anybody with the same issue
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.comwrote:
Perhaps it is defined in a parent pom.
In any case, you can fix this easily by setting
Hi Grant,
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]
On Wed, Apr 28, 2010 at 09:55:05AM +0200, Jörg Schaible wrote:
[snip]
but you should
probably ask the developers of the artifacts in question why they think they
need exactly those versions. Find the artifacts with dependency:tree.
Definitely ask them that. I find that depending on a
I've been in contact with the developer, and the solution is underway.
Thanks, all.
-Grant
On Wed, Apr 28, 2010 at 11:21 AM, Mark H. Wood mw...@iupui.edu wrote:
On Wed, Apr 28, 2010 at 09:55:05AM +0200, Jörg Schaible wrote:
[snip]
but you should
probably ask the developers of the artifacts
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
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
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
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:
12 matches
Mail list logo