On Tue, Nov 26, 2019 at 7:17 PM Karl Heinz Marbaise
wrote:
> Hi John,
>
> On 24.11.19 20:46, John Patrick wrote:
> > i'm trying to start using maven version range more but having issues
> > with things like guava and also it not excluding version i believe
> > should be excluded.
> >
> > 1) i
Hi John,
On 24.11.19 20:46, John Patrick wrote:
i'm trying to start using maven version range more but having issues
with things like guava and also it not excluding version i believe
should be excluded.
1) i don't think this is possible but it might be, take a look a
google guava, it has a
> thoughts?
(I don't design or use Maven version ranges)
I agree that the behavior below, such as "5.0.0-SNAPSHOT" < "5", is not
intuitive for users.
Our team in Google recently articulated good practices of maintaining
dependencies. One of the topics is "not to use version range":
I've recently had the same line of thought...
Many projects publishing "release candidates" or "milestone releases". I
understand
this is great for having feedback from their user base, but sometimes
I'd rather use
a "stable" version. Although this brings a new question to the table:
who
cheers for the information.
I expect this might be asking space vs tabs, but do others feel the
version range of "[4,5)" should exclude anything starting 5, include
5-SNAPSHOT and any 5...-RC* or 5...-alpha
It seams wrong to have to use "[4,4.999)".
I understand from a maths point of
I believe your cases do not work with version ranges. Version ranges depend
on the order of the versions, and thus you cannot filter "-guava".
The ordering of version is defined in
org.eclipse.aether.util.version.GenericVersion in maven-resolver-util.
Example code to check:
//
i'm trying to start using maven version range more but having issues
with things like guava and also it not excluding version i believe
should be excluded.
1) i don't think this is possible but it might be, take a look a
google guava, it has a jre and a android version. using maven version
range
