you could change your range to be [1.0.0-!,2.0.0)
the range you have specified starts with a version without a qualifier. qualified versions are before versions without a qualifier in Maven version ranges... so 1.0.0-v20070606 < 1.0.0 and therefore outside the range you have specified. The issue with including qualifiers is that now -SNAPSHOT builds can be included in the range. The other option is to exclude all the transitive dependencies and add back in the version you want 2008/10/19 Barrie Treloar <[EMAIL PROTECTED]> > How do I work around this type of problem? > > --- CONSOLE LOG --- > [INFO] Failed to resolve artifact. > > Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0) > org.eclipse.equinox:app:jar:null > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > --- CONSOLE LOG --- > > Unfortunately the output doesn't specify which jar caused the > OverConstrainedVersionException. > > Can I just hard code the dependency to the value I want once I find the > culprit? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
