The outstanding feature of this release is that the jar of C5Connector.Java contains the source code of the filemanager. This insures that there aren’t any compatibility issues between C5Connector.Java and the filemanager. We strongly recommend using this feature! The default implementations of the basic interfaces are adapted accordingly.

The changes in detail:

issue #39: Adapt FilemanagerConfig to Filemanager 2.5.

issue #40: Integrate the filemanager source into the jar file

issue #41: New directory with name equals to Parent directory

issue #43: The default implementation of FilemanagerCapability should respect if a file is protected

issue #44: updated filemanager to 2.5.0

issue #45: wrong path in getinfo for folders

This could be one of the last releases of this project. The Filemanager project is deprecated. This is why the future of C5Connector.Java is written in the stars.

Problem: I bought a new VPS and did some configuration changes (e.g. hostname setting). I’ve installed some software and wanted to test if my settings are boot resistant. And every time the VPS was booting the files /etc/hosts and /etc/hostname was overridden by the defaults of the provider.

Reason: Virtuozzo (the software which virtualises my VPS) overrides those files at every time the VPS is booting.

Solution: Replacing the files /etc/hosts and /etc/hostname at boot-time.

The following description is applied for Ubuntu 14.04. Both replacements are implemented as upstart jobs.

/etc/hosts

Copy the /etc/hosts (e.g. /etc/hosts_my) and adapt it to your needs. Then create the file /etc/init/hosts.conf with the following content:

Changes of the configuration of the filemanager can cause errors, because the (default) configuration is provided by C5Connector.Java. To ensure a runnable version, the *-bin.zip contains the source of the filemanager.

The changes in detail:

issue #36: Client and adapter tight coupling (refactored the fetching of the default configuration of the filemanager)