Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369191

Summary:	VersionRangeResolutionException when using defined versions
Product:	z_Archived	Reporter:	Frank Muraschow <frankmur1983>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	frankmur1983, igor
Version:	unspecified	Keywords:	usability
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Frank Muraschow

2012-01-20 05:09:48 EST

Case:

Module A
available versions: 1.0.0, 1.0.1, 1.0.2-SNAPSHOT, 1.0.2, 1.0.3-SNAPSHOT, 1.0.3, 1.0.4-SNAPSHOT


When trying to resolve modula A like this everything works fine:

<groupId>com.xx.yy</groupId>
<artifactId>moduleA</artifactId>
<version>1.0.3</version>


as does this:

<groupId>com.xx.yy</groupId>
<artifactId>moduleA</artifactId>
<version>[1.0.2]</version>



But when trying it like that it doesn't work:

<groupId>com.xx.yy</groupId>
<artifactId>moduleA</artifactId>
<version>[1.0.3]</version>


This is the error I'm getting:
"VersionRangeResolutionException: No versions available for com.xx.yy.moduleA:jar:[1.0.3] within specified range	"



The dependencies are in our remote and in my local repository.

Comment 1 Igor Fedorenko

2012-01-24 09:49:32 EST

Does everything work as expected using maven 3.0.2 on command line? 

Are you able to provide complete standalone project that demonstrates the problem?

Comment 2 Igor Fedorenko

2012-05-21 09:36:04 EDT

Closing old/stale bugreports. Feel free to reopen if you can provide requested information.

Comment 3 Denis Roy

2021-04-19 13:25:14 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/