Hi Erel,
I know this one will probably be shot down, but could a feature be added to B4J so that when building the resultant jar (with "Release") where the Merge attribute has been set to True:
#MergeLibraries: True (which merges all the libraries today)
That a new attribute could be added so that specific jar's could be excluded from the merge? Example as a possible new attribute (which doesn't exist today):
#ExcludeFromMerge: specified jar
example:
#ExcludeFromMerge:bcprov-jdk15on-159.jar
Cases where this would be useful:
For such cases as of the bouncy castle dependency (bcprov-jdk15on-159) which is a signed jar, and when running with #MergeLibraries: True that jar is decompiled and compiled into your jar and therefore losses its signing.
I know this one will probably be shot down, but could a feature be added to B4J so that when building the resultant jar (with "Release") where the Merge attribute has been set to True:
#MergeLibraries: True (which merges all the libraries today)
That a new attribute could be added so that specific jar's could be excluded from the merge? Example as a possible new attribute (which doesn't exist today):
#ExcludeFromMerge: specified jar
example:
#ExcludeFromMerge:bcprov-jdk15on-159.jar
Cases where this would be useful:
For such cases as of the bouncy castle dependency (bcprov-jdk15on-159) which is a signed jar, and when running with #MergeLibraries: True that jar is decompiled and compiled into your jar and therefore losses its signing.