Current Page: NeXtMidas User's Guide Reduced Footprint Builds NeXtMidas With Fewer Third Party Dependencies
| ### Eliminating Third Party Dependencies NOTE: The jars files themselves are still included with the NeXtMidas baseline. The scripts referenced below only swap java code to eliminate the jar dependencies, but the jars don't need to be used after eliminating jar dependencies. bcel jar Used for creating key/value pairs from lambda expressions. This is also used for enhanced logging with LogUtilities.java. From NMROOT, run libnxm/jar-footprint/jar-dependencies/adjust-jar-dependencies.sh nkvpair to eliminate the dependencies on the bcel jar NOTE: The bcel jar is dependent on the commons-lang3 jar, so if the bcel jar is not needed, then the commons-lang3 jar is not needed either. commons-net jar Used for FTP communication From NMROOT, run libnxm/jar-footprint/jar-dependencies/adjust-jar-dependencies.sh nftp to eliminate the dependencies on the commons-net jar lucene jar Used for the popup HELP GUI From NMROOT, run libnxm/jar-footprint/jar-dependencies/adjust-jar-dependencies.sh nhelp to eliminate the dependencies on the lucene jar junit jar The goal is to eliminate the JUnit dependency in the main SYS jar, while keeping it in the SYS TEST jar. Running the script makes the nxm/sys/intr/Unittest.java (used for UNITTEST command) dependent on a Unittest.java in the SYS TEST jar. With the SYS TEST jar in the path, the UNITTEST command continues to work. From NMROOT, run libnxm/jar-footprint/jar-dependencies/junit/move-unittest.sh to eliminate the dependencies on the junit jar