Fix
- [YADE-109] - Replacing should occur once (and not twice) when sending files with jump client
- [YADE-146] - YADE Background Service should store the information on file transfers with files exceeding 2GB
- [YADE-153] - Parameters make_Dirs and source_make_Dirs shall rename source files into new folder
- [YADE-157] - SOSFTPHistoryJob should log errors instead of warnings during import of the transfer history
- [YADE-199] - Parameter overwrite_files=no for existing files should not result in misleading error message
- [YADE-200] - A transferred file should not be deleted in case that a rename is set and the regular expression doesn't match the transferred file
- [YADE-207] - Exceptions should be raised for some reasons even though the parameter force_files=false
- [YADE-216] - parameter for passive mode has no effect when the parameter operation=send is used
- [YADE-231] - YADE CLI jade.sh and jade4dmz.sh script show usage message when invoked without parameters
- [YADE-233] - Receiving files by FTP with recursive=true should transfer files from all level folders
- [YADE-235] - YADE banner header shows incorrect port number and exclusively the source protocol
- [YADE-236] - mkdir in SFTP should create a directory only if it does not exist
- [YADE-238] - YADE should evaluate RegEx for multiple file extensions ^.*\.(xls|csv)$ when used with jump host
- [YADE-239] - YADE should not raise an error "File Not Found" when file_compress=true for use with jump hosts
- [YADE-241] - YADE should generate MD5 hash file when parameter CreateSecurityHashFile = true is set
- [YADE-242] - YADE jump host transfer should work for file names that contain Umlaut ö,ü,ä
- [YADE-243] - YADE does not write local jade_history.log
- [YADE-244] - YADE should create a checksum file for operation "copytointernet"
- [YADE-245] - YADE Client doesn't find its log4j.properties
- [YADE-247] - YADE parameter transaction=true should roll back a transfer if one of the files cannot be written
- [YADE-258] - Error message from FTP server should log if a target file cannot be created
- [YADE-259] - YADE should return an exit code != 0 if an error has occurred
- [YADE-260] - YADE JITL job should be capable to process orders without exhaustion of resources
- [YADE-265] - Environment variables for setup of YADE Background Service History Viewer
- [YADE-267] - Transfer via jump host should work if the installation path of YADE Client is the same as the installation path on the jump host
- [YADE-268] - Option force_files has no efffect
- [YADE-270] - YADE should not show duplicate output of file names in logs
- [YADE-271] - If no files are transferred then the YADE Client should return exit code 0 if this was the expected result
- [YADE-272] - The error SOSJADE_E_0100 should be raised exclusively if no source files have been found
- [YADE-275] - YADE Client logs every line twice if it finds a log4j.properties
- [YADE-279] - YADE should not throw error "no matching file found" when parameter overwrite_files = false is set
- [YADE-285] - Remove domain from YADE banner
- [YADE-288] - Remove typo in the java class name of the Windows jade4dmz.cmd startscript
- [YADE-290] - YADE client connection hangs for FTPS protocol
Deprecation
- [YADE-280] - Retirement of YADE send and receive operations
Feature
- [YADE-173] - YADE should validate certificates for HTTPS and WebDAV
- [YADE-206] - YADE should not raise an exception if the parameters force_files=false and file_path or file_list are used
- [YADE-209] - YADE shall raise a specific exception if an invalid protocol type is used
- [YADE-211] - The setup should create JADE_BIN and JADE_HOME environment variables
- [YADE-230] - Update YADE banner for correct usage of parameters
- [YADE-232] - YADE info log messages should be more concise
- [YADE-240] - Rewrite YADE logging for better overview and debugging
- [YADE-273] - Jump host should be accessible by using a proxy
- [YADE-274] - YADE should support use of a proxy for FTP and SFTP protocols
- [YADE-286] - JADE4DMZ should be able to use http proxy feature with jump hosts
Edit/Copy Release Notes
The text area below allows the project release notes to be edited and copied to another document.