Re: Are released features picked over SNAPSHOT when installing features from maven?

[Steinar Bang <sb...@dod.no>]

>>>>> Steinar Bang <sb...@dod.no>:

> I am working on version 1.15.8-SNAPSHOT of authservice:
>  https://github.com/steinarb/authservice

> My problem with testing release 1.15.8-SNAPSHOT is that 1.15.7 is picked
> instead, when I load feature repositories from maven using version
> LATEST.

> Version 1.15.7 is found on external repos (maven central in this case),
> while 1.15.8-SNAPSHOT is built locally and installed in the local maven
> cache (~/.m2/repository/).

> My questions are:
>  1. Are released versions being picked over SNAPSHOT releases?
>  2. Is this the expected behaviour?
>  3. Is there a simple way to make local feature installs pick SNAPSHOTs
>     over released version?

I have sort of figured it out: it occurs when a feature has a
non-versioned dependency, like e.g. here: 
 https://github.com/steinarb/myapps/blob/master/src/main/filtered-resources/feature.xml#L12

Then the latest released version is picked over the latest snapshot
version, for those features that have released versions.

I was able to fix it internally the authservice application by adding a
version of project.version for all project-internal handwritten feature
dependencies
 https://github.com/steinarb/authservice/commit/1d32fa2b2b465e7fc1985504f7cb06c8e84fd736

But fixing it for myapps above, would require updating versions of the
various features in the myapps project pom and deploying a new version
of the myapps feature when some project get a new release (or a working
on snapshot after a release).

And I kind of like not having to deploy a new version of the myapps
feature every time I change the version of a versioned feature.

Using "LATEST" as the version for feature dependencies didn't work (I
tried).