Hi, we have a number of optional dependencies (bouncycastle, xmlsec, batik and now pdfbox and others) which can be easily not/included on the classpath.
On the modulepath, one need to use the --add-modules argument to activate those modules even when they were declared as "requires static" in the module-info. I would like to make the optional dependencies mandatory. Pro: + users don't need to fiddle around with the maven dependencies and don't need to add add-modules arguments. Neutral: * drive space is not really an issue nowadays Con: - there might be side effects with existing dependencies What is your opinion? Andi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
