[mojo-dev] [jira] (MNBMODULE-245) Dependency resolution for version ranges

[Jesse Glick (JIRA)]

Title: Message Title

Jesse Glick commented on an issue   Re: Dependency resolution for version ranges Right, your module-to-module dependency should always be a single version, the earliest you can possibly support. You can always run interactive/functional tests against later versions if you want. For rare cases you can specify release version ranges explicitly, but few people should need to do this. Whatever you do, do not use Maven version ranges. Add Comment   Mojo's NetBeans Module Maven Plugin / MNBMODULE-245 Dependency resolution for version ranges The dependency resolution mechanism used by the nbm:manifest goal is the same as for the dependency:tree plugin. This means that the version written into the manifest will be the latest available version, considering all artefacts in the reactor. However, the netbeans platform will refuse to load any older version than is written to the manifest. There... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email