Description
The complete patch for this Version can be downloaded from: completePatch.patch
The Changes are also separated available as PATCH in: ./patches/
The Patches are developed in SVN under:
https://bp-cms-commons.svn.sourceforge.net/svnroot/bp-cms-commons/opencms_commons/opencms-patches/trunk
Add Eclipse configs to the Opencms-Project.
- Patch: ./patches/Patch_V7_5_3_antbuild_and_eclipse_configs.patch
- File-Changes:
- /test/test.properties (update: make paths releativ)
- /.settings/org.eclipse.jdt.ui.prefs (new)
- /.settings/org.eclipse.jdt.core.prefs (new)
- /.classpath (new)
- /.project (new)
- /.checkstyle (new)
- Contributor: Harald Brabenetz
Patch for ANT-BuildScripts to deploy the OpenCms-Artifacts to a Maven-Repository after build.
- Patch: ./patches/Patch_V7_5_3_maven-migration.patch
Additional Library: maven-ant-tasks-2.0.10.jar
- File-Changes:
- /modules/build.xml
(update: add MAVEN-ANT Targets)
- /modules/build-single.xml
(update: create source Archives, add MAVEN-ANT Targets)
- /modules/pom-template.xml
(new: pom template for Modules)
- /modules/maven-install.bat
(new: optional helper)
- /build.xml
(update: create source Archives, create opencms-webapp.war without Modules, add MAVEN-ANT Targets)
- /maven-install-with-new-modules.bat
(new: optional helper)
- /maven-deploy-with-new-modules.bat
(new: optional helper)
- /maven-deploy-init-all.bat
(new: optional helper)
- /maven-install-init-all.bat
(new: optional helper)
- /install-nonpublic-libs.bat
(new: install non-public Libraries to the local Repository like JDBC drivers.)
- /pom-opencms-core.xml
(new: pom for opencms-core.jar)
- /pom-opencms-webapp.xml
(new: pom for opencms-webapp.war)
- /pom-opencms-setup.xml
(new: pom for opencms-setup.jar)
- /lib/compile/maven-ant-tasks-2.0.10.jar (new)
(Binary must be manual copied from : maven-ant-tasks-2.0.10.jar)
- Contributor: Harald Brabenetz
If you build OpenCms with Maven, the resulting WAR File will have the name like "opencms-7.5.2.war".
The OpenCms Setup Wizard use the FileName (or Webapp-Context path) as default Schema name.
E.g.: MySql doesn't support "-" or "." inside the Schema name.
This patch replace all "-" and "." with "_" before fill the default-SchemaName on the DB-Setup Screen.
Patch ExplorerType Icon-Name.
If the icon attribute of the explorertype Definition in an OpenCms Modules manifest.xml has no dot, an IndexOutOfBoundsException Exception will occur without information which ExplorerType is wrong.
The error occurs if you want create a new resource in OpenCms.
This Patch checks if the Icon has a dot, and Logs a Warning with detailed information otherwise.
Response: http://lists.opencms.org/pipermail/opencms-dev/2010q2/034222.html
Enable the usage of XSD-Choice Elements in Structured content. Update the XML Content Editor to show, add, move up/down and remove choice elements correctly.
(This Patch should be obsolete in OpenCms 8.0)
- Patch: ./patches/Patch_V7_5_3_XmlChoiceType.patch
- File-Changes:
- /src/org/opencms/workplace/CmsWorkplace.java (update)
- /src/org/opencms/workplace/CmsWidgetDialog.java (update)
- /src/org/opencms/workplace/editors/CmsXmlContentEditor.java (update)
- /src/org/opencms/xml/CmsXmlContentDefinition.java (update)
- /src/org/opencms/xml/CmsXmlContentTypeManager.java (update)
- /src/org/opencms/xml/CmsXmlComplexTypeSequence.java (update)
- /modules/org.opencms.editors/resources/system/workplace/editors/xmlcontent/edit.js (update)
- /modules/org.opencms.editors/resources/system/workplace/editors/xmlcontent/editor_form.jsp (update)
- Contributor: Harald Brabenetz
Improve the FileSelectorWidget Configuration to add an additional filter on ResourceTypes.
Example: configuration="resourcetypeNames=xmlContent,xmlpage"
- Patch: ./patches/Patch_V7_5_3_file_widget_resourcetype_restriction.patch
- File-Changes:
- /src/org/opencms/widgets/CmsVfsFileWidget.java (update)
- /src/org/opencms/workplace/explorer/CmsTree.java (update)
- /modules/org.opencms.workplace/resources/system/workplace/resources/components/widgets/fileselector.js (update)
- /modules/org.opencms.workplace.explorer/resources/system/workplace/resources/commons/tree.js (update)
- /modules/org.opencms.workplace.explorer/resources/system/workplace/views/explorer/tree_fs.jsp (update)
- /modules/org.opencms.workplace.explorer/resources/system/workplace/views/explorer/tree_siteselector.jsp (update)
- /test/org/opencms/workplace/explorer/TestCmsTree.java (new: TestCase for CmsTree with resourcetypeIds Filter)
- /test/org/opencms/widgets/TestVfsFileWidgetConfiguration.java (new: TestCase for CmsVfsFileWidget with Configuration Tests)
- Contributor: Selver Softic
The original cmsshell.bat doesn't work on my computer (Win XP).
I have made several changes to fix this.
- Patch: ./patches/Patch_V7_5_3_CmsShell.patch
- File 1: ./patches/cmsshell.bat
- File 2: ./patches/cmsshell.sh
- Changes in cmsshell.bat:
- replaced "goto gotLib" with "goto gotHome"
I cannot find the target "gotLib" !?
- added: if exist "%OPENCMS_LIB%\opencms-core.jar" goto okLib
The Maven-Build from us creates the JAR-artifact "opencms-core".
It should also work on the original OpenCms distribution.
- replaced complex commandline args concatination with: set CMD_LINE_ARGS=%*
The original code seems not to work!?
The orginal code removes the "=" from Arguments... !?
- removed collecting library variables "OPENCMS_CP" and "TOMCAT_LIB"
not necessary anymore if the java commandline argument "java.ext.dirs" is used.
The original code produced very very long commandlines which cannot be handled by Windows
- Changed Java Command args: removed OPENCMS_CP and TOMCAT_LIB from classpath and add instead: -Djava.ext.dirs=%OPENCMS_LIB%;%TOMCAT_HOME%\lib
The orignal commandline was too long, windows could not handle it.
- Changes in cmsshell.sh:
- removed Windows Linenedings (The PATCH-File cannot handle this type of changes)
- Contributor: Harald Brabenetz
The JQuery DirectEdit Provider can produce an Exception if offsetParent is null (e.g.: in hidden HTML areas like Tabs).
Also all other DirectEdit areas which are place after that area, will not be shown.
The CmsXmlEntityResolver clears his cache on every publish event, even if no schema-definition where published.
Also the LRU Cache has low dimensions (128 row-File-Content Entries and 64 parsed Schema-Definition Entries for the whole online and offline projects).