Änderungen in ccm-bundle sowie ccm-sci-bundle jeweils devel & demo nachgeführt.
git-svn-id: https://svn.libreccm.org/ccm/trunk@1402 8810af33-2d31-482b-a856-94f89814c4df
Beitrag von Terry:
- Neues Import Format fuer terms: SKOS
- Keyphrase extraction utility, nutzbar um Kategorien vorschlagen zu lassen,
die zu einem content item passen.
Update Script:
ccm upgrade ccm-ldn-terms --from-version 6.5.0 --to-version 6.5.1
Es sind Änderungen am theme erforderlich, um die Funktionen nutzen zu können:
siehe:
ccm-ldn-aplaws/src/com/arsdigita/aplaws/ui/TermWidget.java
ccm-ldn-aplaws/web/__ccm__/themes/aplaws/types/ContentTypes.xsl
ccm-cms/web/__ccm__/static/cms/admin/category-step/category-step.xsl
ccm-ldn-navigation/src/com/arsdigita/london/navigation/cms/CategoryDataCollectionDefinition.java
Damit ist trunk hb auf Stand r1902 aplaws trunk
(1871 bis 1876 waren eigene patches, die bereits enthalten sind, ebenso 1894)
Patch 1879 uebersprungen, fuegt dictionary fuer eclipse in das root Verzeichnis
von trunk ein. Da gehoert aber nichts hin, ausserdem Eclipse im Moment nicht
in Benutzung hier.
git-svn-id: https://svn.libreccm.org/ccm/trunk@235 8810af33-2d31-482b-a856-94f89814c4df
by a *.war file and executable in a standard servlet container.
All CCM modules will install into the main application context now.
Backwards compatibilty preserved, ccm scripts can be used as used to.
No update script required for this part.
Modifications:
- application.xml added ROOT as installation target
- base class <module> methods getContextPath() removed, getServletPath() modified
- web.xml-<module>.in created
- import statements in xsl adjusted
- no API change
git-svn-id: https://svn.libreccm.org/ccm/trunk@83 8810af33-2d31-482b-a856-94f89814c4df
r1795: First part of the conversion of CCM to be deployed in a standard way
r1796: Multilanguage categorization (already local, but upgrade script
added, comments and translation added)
First part of the conversion of CCM / APLAWS to be deployed in a standard way
by a *.war file.
Backwards compatible to the procedures so far. The ccm scripts can be used
as used to. Only difference is the location of some files (see below).
As an alternative the webapps directory created by the ccm scripts can be
moved into a standard tomcat container or can be added as a virtual host.
APLAWS no longer depends on all the environment variables. For detailed
instructions see documentation on the WIKI. This is a temporary solution,
further enhancements are on the way!
No update script required for this part.
Modifications:
- Creation of a c.ad.runtime.CCMResourceManager class, which currently
handles just the file locations. It replaces the dependency from the
CCM_HOME environment variable. It is initialized during startup of the
servlet container or by the entry point of the installation tools (i.e.
c.ad.packaging.mastertool). It replaces the c.ad.packaging.CCM class
as well. Currently contains backwards compatibility code to check the
runtime environment just in case the initialization is missing (will be
removed later).
- Creation of c.ad.web.CCMApplicationContextListener class which is
notified by the servlet container at the beginning of the startup procedure.
Initialises CCMResourceManager. Must be configured by web.xml (if a contributed
package overwrites the trunk values)!
- File location changes:
- Configuration registry moved to [appbase]/WEB-INF/conf/registry
- ps2fs files moved to [appbase]/ps2fs
(can be modified by configuration parameter)
- lucene index files moved to [appbase]/WEB-INF/work/lucene
(can be modified by configuration parameter)
Developers watch out! ant clean now removes these files, too (esp. registry)!
- XML factory classes are now determined by configuration parameters
- waf.xml.xsl_transformer=[saxon (default)|jd.xslt|resin|xalan|xsltc]
- waf.xml.dom_builder=[xerces (default) | resin]
- waf.xml.sax_parser=[xerces (default) | resin]
- Package c.ad.packaging reorganized so it contains just installation
related code. Runtime configuration related code moved to c.ad.runtime.
Code is not part of the API.
- log4j configuration file is still at the old location, but is not used
anymore! It will be moved to [appbase]/WEB-INF/conf/ in the future.
Developers, modify the file ~/webapps/WEB-INF//classes/log4j.properties
in the meantime.
- While working on the code some deprecated classes and method invocations
replaced by supported API. If a class is no longer used by any module in
trunk, the class has been removed by appending "nolongerInUse" to the file
name. If any of the contributed modules is still depending on deprecated code
it is easy to find and to follow the recommended replacement instructions. Do
not re-incorporate deprecated code! We have to clean up the code base!
Second part: Multilanguage categories
Added update script
Translation of some comments, added comments
version number bumped to reflect the major changes
git-svn-id: https://svn.libreccm.org/ccm/trunk@73 8810af33-2d31-482b-a856-94f89814c4df
r1661 | chrisg23 | 2007-09-19 09:33:20 +0200 (Mi, 19 Sep 2007)
Include applications on navigation pages where they have been assigned to navigation categories
(currently possible for forums if the optional ccm-categorised-forum module in contrib/wsx is loaded).
git-svn-id: https://svn.libreccm.org/ccm/trunk@26 8810af33-2d31-482b-a856-94f89814c4df
r1645 | chrisg23 | 2007-09-17 17:14:20 +0200 (Mo, 17 Sep 2007)
Example theme files for optional extension to forum application that allows forum instances to be easily placed in site navigation. ccm-categorised-forum is in contrib area under wsx
git-svn-id: https://svn.libreccm.org/ccm/trunk@17 8810af33-2d31-482b-a856-94f89814c4df
r1628 | chrisg23 | 2007-09-17 10:10:40 +0200 (Mo, 17 Sep 2007) | 1 line
Sourceforge patch 1689988 - rather a large commit, but in fact causes very little visible change. Large single commit is necessary because all these changes are essentially atomic.
git-svn-id: https://svn.libreccm.org/ccm/trunk@10 8810af33-2d31-482b-a856-94f89814c4df
r1619 | chrisg23 | 2007-09-13 14:17:59 +0200 (Do, 13 Sep 2007) | 1 line
Sourceforge patch 1793743 changes for aplaws users with config parameter com.arsdigita.cms.category_authoring_add_form=com.arsdigita.aplaws.ui.ItemCategoryPicker to allow categories to be sorted by sortkey or alphabetically - note if you have your own version of category-step.xsl in your theme you need to apply these changes to your theme file in order that tree nodes populated via Ajax are sorted as you expect
git-svn-id: https://svn.libreccm.org/ccm/trunk@4 8810af33-2d31-482b-a856-94f89814c4df
SVN-Version 1.0.5 Rev 1603 + alle meine Änderungen
- Navigation (Adaptive Mode)
- Paginator angeglichen
- Paginator <NoContent> -Tag eingeführt
- manipulate-input.js erweitert für deutsche Umlaute (erste Version)
und vielleicht noch ein paar andere Dinge...
git-svn-id: https://svn.libreccm.org/ccm/trunk@1 8810af33-2d31-482b-a856-94f89814c4df
pb
jensp
quasi