Cyberduck

This is the development home for Cyberduck, a libre file transfer client for macOS and Windows. Command line interface (CLI) for Linux, macOS and Windows. The core libraries are used in Mountain Duck. Source code is available licensed under the GNU General Public License Version 3. Pull requests welcome! For general help about using Cyberduck, please refer to the documentation. The documentation is maintained in its own repository. Additional connection profiles not bundled by default but available in Preferences → Profiles are maintained in its own repository. These are nightly snapshot builds from the current development trunk featuring the latest bug fixes and enhancements. Be warned, though, these builds are potentially unstable and experimental. You can also switch to beta or snapshot builds in Preferences → Update . Manually Visual Studio 2022, following workloads are required: .NET desktop development Universal Windows Platform development Desktop development with C++ Bonjour SDK for Windows Wix v3 (Optional) Remarks : Installing with Chocolatey may or may not fail spectacularly. Following issues have been observed on a clean installation: Bonjour package fails with file not found - though the Bonjour64.msi is extracted from BonjourPSSetup.exe. wixtoolset depends on .NET 3.5-package, which never completes On Windows 11 installation doesn't work visualstudio -workload- may halt with "Operation canceled", Abort Chocolatey-command (Ctrl-C), then open up Visual Studio Installer and Resume installation there System Configuration Make sure that MSBuild , mvn , ant and java are on your PATH -environment variable. Open Developer Command Prompt for VS2022 , then run where msbuild.exe , add first directory name to path e.g. C: Program Files Microsoft Visual Studio Community Msbuild Current Bin amd64 Chocolatey may have added mvn and ant to your PATH -variable The Microsoft OpenJDK 17 installer automatically adds itself to the system PATH . Additionally include the latest Windows Sdk-binary folder in your PATH -environment variable: %ProgramFiles(x86)% Windows Kits 10 bin 10.0. .0 x64 To build on Windows, you need to configure NuGet with credentials to access GitHub Package Registry sources. Create a GitHub personal access token (classic) with at least read:packages permissions. Replace YourUsername with your GitHub username and YourPAT with your personal access token. Run mvn verify -DskipTests -DskipSign to build without running any tests and skip codesign. Find build artifacts in osx/target/release/ .(zip pkg) windows/target/release/ .(exe msi) cli/osx/target/release/ .(pkg tar.gz) cli/windows/target/release/ .(exe msi) cli/linux/target/release/ .(deb rpm) Active the sandboxing profile with -Psandbox to apply sandbox entitlements com.apple.security.app-sandbox . You will run into warnings from MSBuild / WiX that are unrelated to how Cyberduck is built. You may safely ignore them. Build with -Pdebug to allow attaching the remote debugger on port 5005 . Due to Visual Studio not being able to handle Java projects it is required to follow these steps for debugging: Run mvn verify -Dconfiguration=debug which ensures that debugging symbols are generated This prevents Visual Studio (or MSBuild invoked from Maven ) from generating optimized assemblies which in turn may prevent debugging. Open the solution in Visual Studio Open a .java file and set a breakpoint. Visual Studio breaks either on or near the line selected. Debugging capabilities include Step Over Step Into Step Out Continue Local/Auto variables Immediate Window After packaging, run mvn test -DskipITs to run unit tests but skip integration tests. Maven artifacts are available in a repository hosted on Amazon S3. Use the following Maven configuration in your project POM to reference artifacts from Cyberduck YourKit supports open source projects with its full-featured Java Profiler. YourKit, LLC is the creator of YourKit Java Profiler and YourKit .NET Profil