Hi It looks like the auth.core bundle has a uses constraint:
> org.apache.sling.engine.auth; > version="2.0.6"; > uses:="javax.jcr,javax.servlet.http,org.apache.sling.api" I could imagine that due to this uses constraint, the import is hard. Can we fix this constraint ? Regards Felix Am 06.09.2013 um 08:23 schrieb Carsten Ziegeler: > Hi, > > I updated today to the new parent pom 18 which is using latest Maven Bundle > Plugin 2.4.0. > Unfortunately this is now causing problems if DymamicImport-Package is > used, you can see this in the auth.core bundle for example. With previous > versions of the plugin, the Import-Package was calculated with taking > DynamicImport-Package in mind, which means a package declared as dynamic > import was not added to the import list. > With 2.4.0 this changed, and the package is listed in both statements - > while browsing through the docs, it looks to me, that this is the wanted > behaviour nevertheless... > > I'Ve reverted those projects which use DynamicImport-Package (only a few) > to use the older version of the plugin for now. > > But I think this is something we should follow up with the Felix project. > > Carsten > > -- > Carsten Ziegeler > [email protected]
smime.p7s
Description: S/MIME cryptographic signature
