Hi there,
Version ranges are rather buggy at the moment - I've experienced
something similar, although contrary to what you mention:
http://jira.codehaus.org/browse/MNG-2994
Cheers,
Mark
On 16/07/07, ossi petz <[EMAIL PROTECTED]> wrote:
Hallo
another weird problem :)
i have two repositories defined, one for snapshots, one for releases.
when i add a dependency like:
<dependency>
<groupId>group.id</groupId>
<artifactId>artifact-id</artifactId>
<version>[2007.2.,2007.3)</version>
</dependency>
the according jar is looked up in the snapshot repository instead of the
releases repository.
the dependency above has dependant jars itself (like core, logging,
etc). those are downloaded correctly.
only this 'direct' dependency in the current project's pom is looked up
in the wrong place.
adding an explicit version number works normally but that does not solve
my dependency issues.
is there a solution to this? or is it a bug? or did i messed up the
configuration?
any hints appreciated :)
regards
op
---------------------------------------------------------------------
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]
