Jaikiran Pai wrote:
but i guess instead of saying "EXPORT_ALL" (which triggers
the
scanning of jar for packages) we could probably configure each
deployer/deployment to have this file with a set of
"includes"/"capabilities" and explicitly list the packages available?
Probably we could use some MC tool to generate this for a jar file input?
Ales, is this something that could be considered for the MC tools
features that you had in mind?
-Jaikiran