Dantesque WS XML & ENI

0. Introduction 1. zip64 2. Fat jar and executable jar and the MANIFEST.MF is not alone in the META-INF directory 3. Project order, test failure. distTar and distZip duplicated dependencies 4. CommandLineLauncher for avoiding System.exit 5. PDF version from 1.4 to 1.7 (s/Jesus Romero) Including file Ian... 6. java.smartcardio dependency 7. Passing arguments to SimpleFirma.main()  1. zip64 When a large number of libraries need to be included in a fat jar, the zip utility is overwhelmed, so you need to indicate zip64=true when defining a jar task o equivalent jar { zip64 = true duplicatesStrategy = DuplicatesStrategy . EXCLUDE manifest { . . . . . . . 2. Fat jar/Uber jar, executable jar, and the MANIFEST.MF is not alone in the META-INF directory If you want to create a fat jar (uber jar), you must include all the dependencies in the generated jar. There are several options (when you want only a subproject to have a fat jar or if you want that every child project have ...

0. Introduction This file is in the subproject afirma-simple 1. Convert pom.xml to build.gradle Here is the basic build.gradle file, that only needs to define dependencies as in the parent project we have defined the tasks and other definitions  //============================BEGIN======================================================= dependencies { /* Library dependencies part */ api libs . junit /* Project dependencies part */ api ( project ( " :afirma-core " ) ) } //==================================END================================================= The yellow marked code is the one you must change or add elements Let's see the pom.xml from the project " afirma-crypto-ooxml " //============================BEGIN======================================================= <? xml version = " 1.0 " encoding = " UTF-8 " ?> < project xmlns = " http : // maven.apache.org /POM/4.0.0 " xmln...