Hi, Carsten Ziegeler schrieb: > Stefano Lenzi wrote: >> Hi All, >> >> After the new release of the org.osgi.core:1.2.0 and >> org.apache.felix.bundlerepository:1.2.0, the trunk do not compile >> anymore if you download felix from the SVN with an empty .m2 maven >> repository. In fact, several bundles dependes on >> org.osgi.core:1.1.0-SNAPSHOT which has never been released so they fail >> to compile. >> >> I have create the issue FELIX-715 and I have attached a simple patch. >> There are two possible solution modify the dependencies to the new >> 1.3.0-SNAPSHOT version or bind the dependencies to on of the 1.0.X >> release. I think that for org.osgi.core artifact every project should >> point to the released version, while for the bundlerepository artifact >> it is better to depend on the latest SNAPSTHO. Of course the final word >> is own by the main developer of the particular artifact. Furthermore, we >> may start to use the version range feature provided by maven. WDYT? > I think we should just all point them to the released version (1.2.0 for > all of them). If there is a need to update to a snapshot one can do it > easily.
Agreed with referring to released versions. But we should refer to the minimal released version acceptable for the respective module. The reason for this is the maven bundle plugin and bnd, which create the Import-Package declaration with versions from the dependencies. So if we include a dependency to o.o.framework of the o.o.core 1.2.0 bundle, we get a required package version of 1.4. This is only usefull, if we really use functionality from the framework API 1.4 (OSGi Core R4.1). If all we use (and require) is framework API 1.3 (OSGi Core R4.0) we should definitely only depend on the o.o.core 1.0.0 bundle. Regards Felix
