Hi,
On 23/09/16 18:38, Robert Patrick wrote:
What I am questioning is the "engineer's approach" to version range resolution
without
> a valid use case for why Maven should consider
> pre-released versions as within the "not including 2.0" version
> range semantics.
The simple answer to this is the timeline of those releases...
So a pre-release (2.0-alpha-1, 2.0-RC1 etc.) will be done before the
final release (2.0) so must be defined as before...
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
