Thanks. I've rewritten the PR under the assumption that all version
ranges are "hard". Please take another look. (PTAL)
On Fri, Nov 1, 2019 at 7:54 PM Stephen Connolly
wrote:
>
> On Fri 1 Nov 2019 at 21:37, Elliotte Rusty Harold
> wrote:
>
> > Pass 1:
> >
On Fri 1 Nov 2019 at 21:37, Elliotte Rusty Harold
wrote:
> Pass 1:
> https://github.com/apache/maven-site/compare/master...elharo:patch-34
>
> This might not be accurate. In particular I am assuming that if there
> are two requirements for [1.0,2.0] and (3.0,5.0) that something will
> be picked.
Pass 1: https://github.com/apache/maven-site/compare/master...elharo:patch-34
This might not be accurate. In particular I am assuming that if there
are two requirements for [1.0,2.0] and (3.0,5.0) that something will
be picked. This might not be accurate. If this instead fails the
build, please
On Tue 22 Oct 2019 at 11:30, Elliotte Rusty Harold
wrote:
> The docs at
> https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification
> say:
>
> 1.0: "Soft" requirement on 1.0 (just a recommendation, if it matches
> all other ranges for the dependency)
> [1.0]: "Hard"
The docs at
https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification
say:
1.0: "Soft" requirement on 1.0 (just a recommendation, if it matches
all other ranges for the dependency)
[1.0]: "Hard" requirement on 1.0
However, I don't think anywhere do we actually explain what
