A simple Java FTP-Client program
A side project to practise my Java skills and to help improve my GUI skills. It is a GUI drag-and-drop application that is currently only supported on Linux. It can be installed on Windows with workaround steps, but no testing has been carried out on that OS.
Note that this has only been testing on Unix based FTP servers due to limited resources
These features are as of release 1.1.0
- Browse files on both the local file system and the remote FTP System
- This is done using a panel to list the files in the current directory on that File System
- Works much like a shell terminal, you operate within it in a directory, this is the panel's current directory
- Open simple text files in a very basic editor
- Opening certain files causes the program to crash. Therefore, the editor is extremely experimental. If the program crashes upon opening a file, open a bug report outlining the file extension and type (don't have to include contents). This will be a type that needs to be added to the list of files that cannot be opened.
- Allow saving of these edited files
- Absolute and relative paths can be specified in any dialog requesting a path. The PathResolver interface provides this resolving of paths, where each implementation can define how the path is resolved. In most cases, this means to convert it to an absolute, canonicalized path (i.e. no . or .. characters and all symbolic links expanded to target path)
- Creation of new files/directories on both local and remote server. Creation of symbolic links on the local machine.
- Deleting files and directories (recursively)
- Viewing of basic file properties such as modification time, size, permissions etc.
- Applying a mask to the list of current files to filter them using wildcards like * and ?
- Navigating by using the file panels or entering a specific path using the Go To button
- Support for symbolic links (limited support, see the entry on Symbolic Links)
- Support for showing/hiding hidden files (if supported on local file system, remote file system, filename just needs to start with a dot character)
- Renaming files (this can also be used to move files)
- Copying/moving/deleting files (non-recursive and recursive)
- Saving/Deleting sessions (the server that was logged in, last working directory etc.)
- Login panel to the server
- Drag and drop copying of files and folders as well as dialog options to do the same
- Viewing background tasks and their statuses
- Caching of remote directory listings
- Multi-selection of files. These multi-selected files can be chosen by single clicking the icon on the left hand side of the file icon or by Ctrl+clicking the file
You need the following to run the application:
- For runtime (no development):
- Java JRE 11 minimum
- For development:
- Maven 3.6.3 if you don't want to use wrapper
- Java JDK 11 minimum (all other dependencies resolved automatically by Maven)
- For both:
- JavaFX Runtime Components minimum 11.0.2, install here if you want to install globally: https://openjfx.io/openjfx-docs/#install-javafx
- In a directory where you want to download the project, call git clone using the clone url (or download the zip and extract to a specified directory)
- Using system-installed maven, call mvn or the maven wrapper for your OS
- Called mvn (or ./mvnw) clean install
- The built jar will be in the target folder
All installation artifacts are in /install in the project root.
This uses the simpleftp_install.sh script. It has the following options:
- -v (as seen in GitHub releases)
- -j (location of the jar file) Either -v or -j can be provided (not both). If both are omitted, this attempts to install the latest release. The -j flag can be used to install a JAR that you have built following the build instructions.
- -o (specifies the directory to install the program to, defaults to current directory) If this directory isn't accessible by the current user, the script needs to be run with sudo privileges.
- -h (displays help information on the arguments)
- -javafx (Used to specify the installation of JavaFX runtime lib folder) This can be used if you get an error that the module path requires module path specification. This is because the script couldn't determine the installation directory.
- -d (Enables debugging information to be displayed from the installed program)
- -i (This flag specifies that the JavaFX runtime should be installed to the output directory). The -javafx and -i flag can't be both specified.
The script creates a simple_ftp script which can be double clicked (if your linux operating system is configured for this) or run from the command line. This script can be moved to any location provided the installed JAR (and JavaFX components if specified) stay in the same location.
- If JavaFX Runtime is installed globally either have PATH_TO_FX environment variable called before running the script, or specify the location of the lib folder with the -javafx argument
- Launch the script (if you want the latest version, omit the -v and -j flags)
- If there are existing simple-ftp jars in the output directory, you will be asked individually if you want to remove them. It is recommended to remove them and only have the single updated JAR file to avoid conflicts.
- After this, on successful installation, there should be a script simple_ftp in the output directory, and it should be executable.
- If there is a password.encrypt file in the output directory, it means it got left behind. Remove it.
- If you want to install JavaFX run-time just for this installation, use the flag -i. After installation, in the output directory, there should be a folder called javafx-sdk-11.0.2. If this inadvertently gets removed, re-install the application with this script.
- If you don't want the latest version, go to the GitHub repository and see the released versions and enter the desired version number.
If you are updating the file or re-installing the JAR, before running the script, open the installed JAR in where you previously installed it, open the password.encrypt file and copy the contents into a backup file. After the new JAR is installed, open the new JAR, then the password.encrypt file and clear it. Paste the old key value in again. This is required as your session file (installed in $HOME/.simple-ftp/sessions.xml) will not work with a changed password.encrypt file.
Do not re-install in a different location as this will not work with your session file and you may inadvertently remove it for the other installation.
- You need the password.encrypt file on the classpath containing a 20 character key for encrypting passwords.
- It is best to have this file inside in the Jar, or else run export (set on windows) CLASSPATH=<folder containing password.encrypt (not the file name)>:$CLASSPATH(%CLASSPATH% on windows)
- You can specify a system property to provide a different name or specific path to the file (see Configuration properties)
- Create a text file called password.encrypt.
- Edit the file and add in a string of 20 random characters.
- In the same directory where the jar is located, move the password.encrypt file to it
- Run the command jar -uf password.encrypt. Example is jar -uf simple-ftp-1.0-SNAPSHOT.jar password.encrypt. (1.0 may be a different version number)
- Run jar -tvf and verify that a file called password.encrypt is in the root of the jar
- Delete all copies of password.encrypt that are not inside in the JAR (if not having it inside the jar, ensure there is only one copy in the location on the classpath or specified by the property)
You need the JavaFX runtime components to run this application. Follow these instructions: https://openjfx.io/openjfx-docs/#install-javafx. I recommend you set the PATH_TO_FX variable in the same place you set your PATH variable on startup (e.g in Windows system variables or Linux in .bashrc, .profile etc)
Or use the -i flag on install script for a local version of JavaFX (It is recommended to install system-wide however)
If the jar command could not be found, you have a JRE installed instead of JDK, you can use the zip command (as a JAR file is just a ZIP).
For adding the file, replace the jar -uf command with the zip -u command with the same order of arguments. To list the files, use unzip -l command and see if the file is included. All other steps still stand (e.g. password.encrypt must be in the same directory etc.)
In the installation directory, double-click simple_ftp or in a terminal launch the script. That should be enough to open the application.
If you get errors saying module path requires module path specification, see the installation steps on how to resolve it. If you get errors saying failed to find javafx.controls, either the JavaFX runtime components are not installed correctly, or the path provided by the PATH_TO_FX or by -javafx flag is incorrect.
If the file is not added to the jar, you need to add the file's location to the CLASSPATH
For example, if a folder called resources contains the password.encrypt file, you want to add the absolute path to the resources folder to the classpath. Don't add the file in the path on the classpath. If the path it /path/to/resources/password.encrypt, you will want to add /path/to/resources to the CLASSPATH.
If the name of the file is different to password.encrypt, the name of the file needs to be specified by the -Dsimpleftp.passwordEncryptFile= property.
You can also specify the full path to the file here, e.g. -Dsimpleftp.passwordEncryptFile=/path/to/resources/password.encrypt
e.g. classpath You have a directory called simpleftp/resources and inside in the resources you have the password.encrypt file. Add the following to classpath CLASSPATH=jar-name:simpleftp/resources
If it cannot find the file in any of these, it attempts to find it in the directory returned by the system property "user.dir".
WARNING: If this file changes, any existing encrypted passwords in files will not work anymore.
You can enable debugging information by running with the property -Dsimpleftp.debug
After installation on Linux, you will see this file in the installation directory. It provides a range of configuration options. The file is commented with the values expected and their function.
Symbolic links are experimental as not every operating system supports them and depends on the FTP Server if they are supported or not. So, because of this support issue among different systems, it's hard to have a consistent experience with symbolic links.
There may be bugs/unexpected behaviour with symbolic links that were not anticipated during development. Any bugs/issues that are found however, should be reported so that they can be worked on and see if a solution can be worked on them.
In the future, it may be a possibility to implement some form of abstract symbolic link for systems that don't support links. These links would only exist within the application and would have to be stored somewhere. Maybe in a different XML file than the Session xml file for saving sessions (or in the session file, as you may want different links on a different server). However, for now, we can only support symbolic links if they are supported on the relevant system/server.
The following features for symbolic links supported are:
- Following a symbolic link (i.e. following it as if it is an actual directory/file in the current directory)
- Following a link directly to its target instead of following it symbolically
- On a local panel, you can create a new symbolic link.
- On a remote panel, you can click create symbolic link but it just gives directions how to
- Navigating to symbolic links from entering the path in the go to dialog (for directories, gives the option to go to the path (follow), or go to the target)
- The size of the symbolic link displayed is the size of the actual file it points to. This is contrary to a linux symbolic link for directories, but I believe showing the actual size is better. (Configurable in simpleftp.properties)
This project has just been migrated to GitFlow (https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow). Initially all commits were on master, but all of them have been moved to develop. As of 8th December 2020, all development will be done off the development branch with feature branches etc