On 17/05/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Sounds like a bug to me...
Have a look at http://jira.codehaus.org/browse/MNG-2988 and see if
that makes sense.
Cheers,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
Sounds like a bug to me...
On 17/05/2007, at 9:02 AM, Mark Hobson wrote:
Hi there,
I'm working on tests for MRELEASE-177 which has led me to investigate
how ranges are resolved. An example problem was [1.0,2.0] resolving
to 2.0 irrespective of the repository metadata.
This appears to be due
Hi there,
I'm working on tests for MRELEASE-177 which has led me to investigate
how ranges are resolved. An example problem was [1.0,2.0] resolving
to 2.0 irrespective of the repository metadata.
This appears to be due to VersionRange.getSelectedVersion and
isSelectedVersionKnown which selects
I'm trying to resolve mdep-50. Inside the dependency plugin, I use
public Artifact createArtifact( String groupId, String artifactId,
String version, String scope, String type )
to create the artifact. I pass in the range from the plugin
configuration ( [3.7,4.0) for example ) directly to this
