Re: [equinox-dev] Uses constraint violation: -clean doesn't find solution even though it exists

For awareness,   I am looking at it, but will be a bit slow while at EclipseConverge and Devoxx.  Looking at the problem it seems that the resolver should find a solution pretty easily but the presence of one of the versions of org.apache.httpcomponents.httpcore_4.4.4.v20161115-1643 (there are thre

Re: [equinox-dev] Uses constraint violation: -clean doesn't find solution even though it exists

Hi, > Having only one exporter of a package is generally the best way to avoid > choice :-) I know. Sadly, that's not a (short term) solution to this particular problem (see below). > The import [4.2.1,4.4) seems very odd. Why the upper limit on 4.4? This > seems to ignore semantic versioning. I

Re: [equinox-dev] Uses constraint violation: -clean doesn't find solution even though it exists

Having only one exporter of a package is generally the best way to avoid choice :-)   The import [4.2.1,4.4) seems very odd. Why the upper limit on 4.4? This seems to ignore semantic versioning. I would have expected [4.2,5). Similarly [4.3.3,) is too broad. I would have expected [4.3,5). These ver