Hello,
the maven-bundle-plugin by default generates import statements for maven
dependencies with a version range like "[3.0,4)" for a project dependency
that is declared like this:
<dependency>
<groupId>my.group</groupId>
<artifactId>my-artifact</artifactId>
<version>${project.version}</version>
</dependency>
In this case the exact version (3.0.0.SNAPSHOT) of the dependency is known
and still the version range is used for the import.
I found other threads and JIRA tickets discussing the ordering of versions
with and without classifiers (SNAPSHOT or else) and what would be included
in a given version range and what not. But I have not found information as
to why the ranges are used in the first place if the exact version of a
package is known?
Could someone point me to a resource explaining this?
Also, the discussions mention that it is possible to declare the exact
version of an import. I know that I can do it on a package by package basis
in the <Import-Package> section of the plugin configuration.
Is there a configuration option that enables this globally where exact
versions are known?
Thanks!
Ralf
--
View this message in context:
http://apache-felix.18485.x6.nabble.com/Why-import-version-range-if-exact-version-of-dependency-is-known-tp5010123.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
