Am 06.07.2017 um 21:21 schrieb Niels Thykier: > Hi, > > Can we do anything to improve its detection accuracy? If not, I suspect > it might be better to simply remove the check if newer packaging > practises have made it (mostly) obsolete. I'm not sure. For Maven projects the check could be removed I think. If at all it is only useful if you package applications that depend on multiple libraries and you need to write your own start script. But even then it is not strictly necessary to have a Manifest file with a classpath somewhere, you can just use the -cp command line flag and point to a directory that contains all necessary jar files. (just did that for pdfsam where the classpath is set to /usr/share/pdfsam/lib. I believe if we could narrow down the check to applications it would be more useful because I see too many warnings in library packages where I think they are not really needed. But on the other hand the check seems to target Java libs. I just can't make sense of the last sentence here: "Failing to do that means that for every change in class path, all rdepends must update their wrapper scripts, which is a lot of work for nothing." Can someone give a concrete example? Markus
Attachment:
signature.asc
Description: OpenPGP digital signature