Activity for Christoph
-
Christoph committed [45d004] on Code
use version catalog
-
scrutinizer: switch to Java 17
-
remove lgtm.com references because it is integrated in GitHub now
-
disable docker based FTP tests because they fail on Mac and GitHub rn
-
update to Gradle 8.2
-
update GitHub build to Java 17
-
build updates
-
fixed formatting
-
don't propagate the property vfs.sftp.sshdir (used by tests) to a static variable used for every connection later
-
separate FSFile::getPath into getFsAbsolutePath and getDisplayPath
-
random code updates
-
dependency updates
-
remove usage of the commons VFS FileType enum
-
refactor FileObjectChooser to hide all vfs references inside
-
rename File to FSFile to remove the java.io.File name clash
-
reorganize packages
-
rename AbstractBufferedFile and AbstractFile because neither is abstract
-
refactor so that both FileSystemConnections and BufferedFileSystemConnections are looked up using guice
-
merge Site into FileSystemConnection
-
Let FileSystemManager look up FileSystem implementations using Guice
-
deduplicate XML parser / serializer creation code to create secure parsers centrally
-
fix about dialog license list
-
misc code improvements
-
fix windows style path support
-
add spotbugs
-
add some todo comments for nested SWT event loops
-
more records
-
some records
-
fix formatting
-
Java 15 -> Java 17 & Guice 5.0.1 -> 5.1.0
-
code style
-
code cleanup (up to Java 15)
-
no more travis
-
fallback to Java 15 because of Guice
-
Update readme to 2022
-
update project dependencies
-
gradle updates
-
refactor away direct vfs2 dependency
-
apache commons vfs: exclude org.apache.hadoop dependencies
-
add README.md
-
add SFTP test using testcontainers.org
-
add back the tests for the local filesystem
-
switch jUnit 5 to the junit-jupiter combined dependency
-
add v1.1 profile deserialization test
-
website cleanups
-
update eclipse formatter definition
-
Year 2020
-
remove unsupportable 32bit version
-
remove deprecated API use
-
code cleanup
-
Update Gradle to version 6.0.1
-
fix some Gradle 7 incompatibilities
-
fix typo in SimplifiedRuleSetDescriptor and SimplifiedSyncRules
-
Bump commons-vfs2 from 2.4.1 to 2.5.0
-
Bump gradle-versions-plugin from 0.25.0 to 0.27.0
-
update Eclipse SWT from 3.106.3 to 3.113.0
-
TaskDecisionList: fix exception because of disposing images in the ImageRepository
-
AboutDialog: fix missing license contents
-
fix default port value for URLs without port
-
code style
-
extract ScheduleTaskSource from ProfileManager
-
code style
-
more immutable classes
-
refactor the TaskGeneratorImpl
-
extend ProfileManager tests
-
Profile: only store last error data if it is not empty to align with test expectations
-
NiceListView: refactor profile reference out of the ContentComposite
-
refactor out XML child NodeList usage into XmlUtils.forEachChildElement
-
ProfileManager: update triggered events to also trigger a ProfileChanged event for updateProfile calls
-
refactor NiceListView classes to remove the ContentComposite class
-
code style
-
FilesystemTestBase: cleanup
-
ProfileManagerSchedulerTaskFactory::create: fix parameter name
-
add GitHub Action to verify Gradle Wrappers
-
Upgrade Spotless to 5.1.1 and migrate to the new coordinates
-
fix reflection warning
-
Please attach the log file in %USERPROFILE%.config\fullsync (enter this in explorer)
-
Yes I am considering fixing this, but I still can't give you a specific release date. Contributions are always welcome tough! BR, Christoph
-
Hi Kevin, have you tried uploading files with FileZilla or just tried to connect? From the log it looks like FullSync is able to connect but fails to upload a file because the server denies that. BUT: FTP is a horrible protocol. If at all possible use SFTP (filetransfer over SSH - not to be confused with FTPS which is just horrible FTP with TLS). I assume that you can SSH into your EC2 instance already, so using SFTP would remove an additional service that you need to expose to the internet. BR,...
-
Hello Jan, The version of FullSync installed by the windows installer is 32bit only. The Java VM you use is 64 bit, thus FullSync doesn't start. Also I'm not sure if the released FullSync version will run with Java 11. Also I suggest using the semi official OpenJDK builds from https://adoptopenjdk.net/releases.html istead of Zulu. On that page select OpenJDK 8, HotSpot for Windows x86. If you prefer to use a 64bit Java VM you can get FullSync with 64bit support by using the "FullSync without Installer"...
-
drop com.mindtree.techworks.infix.pluginscommon.test.ssh.SSHServerResource source
-
set versions with variables
-
Hi, drop the attached jar file into the /home/eric/Bureau/FullSync-0.10.4/lib/ folder and you should be good to go! BR, Christoph
-
This i slikely caused by an incompatibility of FullSync with more recent Linux Distribution releases... I'll see if I can update that this weekend and let you know. BR, Christoph
-
update Sonarqube from 2.6.2 to 2.7
-
update Spotless from 3.22.0 to 3.23.0
-
fix a few lgtm.com issues
-
update Gradle from 5.2.1 to 5.5.1
-
use the gradlePluginPortal() DSL method to refer to the Maven repository for Gradle Plug-Ins
-
also execute spotlessCheck during the travis build
-
update hamcrest from 1.3 to 2.1
-
Update to Gradle 5.2.1
-
mvn-infix-junit-sshd: add javax.xml.bind:jaxb-api dependency
-
disable coveralls on openjdk11 due to TLS error
-
update io.pry.gradle.offline_dependencies from 0.4 to 0.5.0
-
Update to Gradle 5.1.1
-
add java 10 tests
-
ProtocolSpecificComposite::getConnectionDescription(): remove URISyntaxException that is not possible any more
-
cleanups
-
move ProfileDetails related classes into a separate package
1 >