What's the best way to test the validity of version-ranges in maven builds? For example, let's say I have a module that depends on slf4j versions [1.5.0,1.7.0). I think that the only way to be confident that the range is correct is to build and test against various versions in that range. Is there a way to get maven to attempt to build the module using the earliest and latest version in the range? How about multiple versions? How about ranges for multiple libraries?
Asked
Active
Viewed 229 times
1
-
If you are heading that way, wouldn't you need then to test all possible combinations of library versions. Otherwise, this idea doesn't make sense. – Dmitry B. Nov 12 '11 at 01:41
-
I don't think so, but it couldn't hurt. – Craig P. Motlin Nov 22 '11 at 17:50