Re: Is there a cache of version range resolutions?

[Benson Margulies]

I use 3.2.5. I've since confirmed that version ranges don't work the
same way as the release plugin, so in some sense this problem is moot.
But, still, the problem is the mysterious caching of a
previously-selected version.

On Sun, Oct 4, 2015 at 5:07 PM, Karl Heinz Marbaise  wrote:
> Hi,
>
> On 10/2/15 11:06 PM, Benson Margulies wrote:
>>
>> I've just tried version ranges for the first time, and I hit a pothole.
>>
>> Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.
>>
>> Step 2: change version in pom to  [7.13.500.c52.2,7.13.600.c52.2).
>>
>> Now, mvn dependency:whatever shows the correct resolution, but an
>> actual build stubbornly uses the 7.14.0.c52.2 version in the
>> karaf-maven-plugin.
>
>
> Which Maven version do you use?
>
> Kind regards
> Karl Heinz Marbaise
>
>>
>> Completely wiping ~/.m2/repository fixed this.
>>
>> Can anyone give me higher-precision coordinates for what data I need
>> to nuke when this happens?
>>
>> -
>> 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

Re: Is there a cache of version range resolutions?

[Karl Heinz Marbaise]

Hi,

On 10/2/15 11:06 PM, Benson Margulies wrote:

I've just tried version ranges for the first time, and I hit a pothole.

Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.

Step 2: change version in pom to  [7.13.500.c52.2,7.13.600.c52.2).

Now, mvn dependency:whatever shows the correct resolution, but an
actual build stubbornly uses the 7.14.0.c52.2 version in the
karaf-maven-plugin.


Which Maven version do you use?

Kind regards
Karl Heinz Marbaise



Completely wiping ~/.m2/repository fixed this.

Can anyone give me higher-precision coordinates for what data I need
to nuke when this happens?

-
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

Is there a cache of version range resolutions?

[Benson Margulies]

I've just tried version ranges for the first time, and I hit a pothole.

Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.

Step 2: change version in pom to  [7.13.500.c52.2,7.13.600.c52.2).

Now, mvn dependency:whatever shows the correct resolution, but an
actual build stubbornly uses the 7.14.0.c52.2 version in the
karaf-maven-plugin.

Completely wiping ~/.m2/repository fixed this.

Can anyone give me higher-precision coordinates for what data I need
to nuke when this happens?

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is there a cache of version range resolutions?

[Stephen Connolly]

IIRC don't version ranges only work with Major.Minor.Patch-(Qualifier or
Build) formatted version numbers, eg 3.2.1-07

On Friday 2 October 2015, Benson Margulies  wrote:

> I've just tried version ranges for the first time, and I hit a pothole.
>
> Step 1: set version in dependency to: 7.14.0.c52.2. Run a build.
>
> Step 2: change version in pom to  [7.13.500.c52.2,7.13.600.c52.2).
>
> Now, mvn dependency:whatever shows the correct resolution, but an
> actual build stubbornly uses the 7.14.0.c52.2 version in the
> karaf-maven-plugin.
>
> Completely wiping ~/.m2/repository fixed this.
>
> Can anyone give me higher-precision coordinates for what data I need
> to nuke when this happens?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
> For additional commands, e-mail: users-h...@maven.apache.org
> 
>
>

-- 
Sent from my phone