OX6:6.22 Packaging Changes - Revision history

Choeger: Choeger moved page 6.22 Packaging Changes to OX6:6.22 Packaging Changes

2015-11-27T09:24:25Z

Choeger moved page 6.22 Packaging Changes to OX6:6.22 Packaging Changes

← Older revision

Revision as of 09:24, 27 November 2015

Sonja.krause-harder at 18:57, 27 September 2012

2012-09-27T18:57:12Z

← Older revision		Revision as of 18:57, 27 September 2012
Line 1:		Line 1:
	= Packaging changes in Open-Xchange Server v6.22 =		= Packaging changes in Open-Xchange Server v6.22 =

	== Configuration file location ==		This page describes changes to our configuration directory layout. This is important if you have custom plugins for your Open-Xchange Server systems which you are maintaining and packaging yourself as RPM or Debian packages.

			If Open-Xchange has built and is maintaining custom packages for you, please check with your contact person at Open-Xchange when updated packages will be available.

			= Configuration file location =
	In v6.22 we simplified the directory tree containing all configuration files to not longer include the subdirectories <code>admindaemon</code>, <code>common</code> and <code>groupware</code>.		In v6.22 we simplified the directory tree containing all configuration files to not longer include the subdirectories <code>admindaemon</code>, <code>common</code> and <code>groupware</code>.

Line 14:		Line 18:
	If you are accessing configuration files from your own Java code by absolute path, you are of course free to move these files to our new directory layout or just leave them where they are.		If you are accessing configuration files from your own Java code by absolute path, you are of course free to move these files to our new directory layout or just leave them where they are.

	== Theme packages ==		= Theme packages =

	In v6.20 and earlier, custom themes were registered in the file		In v6.20 and earlier, custom themes were registered in the file

Sonja.krause-harder at 18:51, 27 September 2012

2012-09-27T18:51:32Z

← Older revision		Revision as of 18:51, 27 September 2012
Line 14:		Line 14:
	If you are accessing configuration files from your own Java code by absolute path, you are of course free to move these files to our new directory layout or just leave them where they are.		If you are accessing configuration files from your own Java code by absolute path, you are of course free to move these files to our new directory layout or just leave them where they are.

	= Theme packages =		== Theme packages ==

	In v6.20 and earlier, custom themes were registered in the file		In v6.20 and earlier, custom themes were registered in the file

Sonja.krause-harder: Created page with "= Packaging changes in Open-Xchange Server v6.22 = == Configuration file location == In v6.22 we simplified the directory tree containing all configuration files to not longe..."

2012-09-27T18:51:09Z

Created page with "= Packaging changes in Open-Xchange Server v6.22 = == Configuration file location == In v6.22 we simplified the directory tree containing all configuration files to not longe..."

New page

= Packaging changes in Open-Xchange Server v6.22 =

== Configuration file location ==
In v6.22 we simplified the directory tree containing all configuration files to not longer include the subdirectories <code>admindaemon</code>, <code>common</code> and <code>groupware</code>.

If one of your custom packages contains a configuration file which needs to be read in by Open-Xchange Server, you need to install this file now in the new location. This is typically the case for UI plugins which add some server configuration. In v6.20 and earlier, these plugins used to put their configuration files below:

/opt/open-xchange/etc/groupware/settings

Now these files need to be put in:

/opt/open-xchange/etc/settings

If you are accessing configuration files from your own Java code by absolute path, you are of course free to move these files to our new directory layout or just leave them where they are.

= Theme packages =

In v6.20 and earlier, custom themes were registered in the file

/opt/open-xchange/etc/groupware/settings/themes.properties

by adding a line following this format:

modules/themes/customtheme=Custom Theme

In v6.22 and later, every theme installs its own configuration file:

/opt/open-xchange/etc/settings/customtheme.properties

The format of the this file is unchanged, so it would still contain the one line documented above.

If you have made changes to the file <code>themes.properties</code> in 6.20.7 or earlier, the changed file will be moved to the new location and you configuration will continue to work.