MOHSIN m:
I know portal dependency jar is depricated in liferay 7 but how
about bnd attribute like Export-Package,Import-Package,.. that I
guess we can specify.
Yes, you can add any of the bnd.bnd directives into the
liferay-plugin-package.properties and they'll get picked up.
MOHSIN m:
I have a WAR project where in all my jars are pulled in gradle
file, while building it is giving me "Unresolved
requirement: Import-Package: bsh" issues which I can handle
in liferay-plugin-package.prop file by specifing
Import-Package= !bsh -is that right?
Almost, it is actually like:
Import-Package=!bsh,\
*
The last line is important; the previous lines tell OSGi what you
aren't going to import, but you need the last line to say it's okay to
import everything else.
MOHSIN m:
And how about jar which is not avaialbe in any repo(Custom
jar); how can I make it available to my war portlet.
So for those, you want to use the compileOnly Gradle directive. This
will allow your code to build, but will not be included in the war.
When deployed, as long as the dependency is satisfied within the OSGi
container, OSGi will happily wire it in for your WAR-based module.
