• last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-2913: Remove test sources and build tasks from LAMS projects.

  1. … 294 more files in changeset.
LDEV-2847: Major changes to build.xml files. See JIRA comment for full explanation.

  1. … 1191 more files in changeset.
LDEV-2839: Make JSP precompilation task independent of schemaexport.classpath Ant variable which does not exist and is not needed in all projects.

  1. … 26 more files in changeset.
LDEV-2839: Simplify choosing files for WAR with precompiled JSPs. Current solution creates unnecessary tree of empty directories where JSPs were located. The advantage is that special directories in Tools like Wiki (wikiling plugin) or Videorecorder (previewImages and recordings) do not need to be listed explicitly for compilation which allows generic Ant task for Tools and other projects.

  1. … 26 more files in changeset.
LDEV-2839: Create Java source folder if it was not created in previous step (Java files generation from JSPs) to prevent compilation errors.

  1. … 6 more files in changeset.
LDEV-2839: Turn off debugging in generated classes. This reduces size of WAR almost by half.

  1. … 3 more files in changeset.
LDEV-2839: Adjust JSP precompilation settings as it will be used mainly for production, not development environment.

  1. … 1 more file in changeset.
LDEV-2839: JSP precompilation mechanism adjustment: If there are other compiled classes in source WEB-INF folder, do not take them for WAR assembly.

LDEV-2839: Forum Tool clean up: Set compile output folder same as in other projects. Make "clean" task less verbose while doing the same thing.

  1. … 1 more file in changeset.
LDEV-2839: Allow JSP precompilation in Forum Tool.

  1. … 2 more files in changeset.
LDEV-2823: Add properties that select whether standalone or embedded MySQL should be used for LAMS run and/or build.

Make all Tools use MXJ connectors if needed.

Make Tool Deployer usage lighter - libraries are not copied to Tools but they are referenced from a single spot.

Copy MXJ connectors from "mysql_embedded" project if needed.

  1. … 50 more files in changeset.
LDEV-2577

The new CKEditor does not have Java Integration library (yet). We have been

using it to:

a) get the tag library to create our own tag <lams:FCKeditor>

But the new CKEditor uses AJAX to get the contents, so the library is

not needed anymore.

The references to it has been deleted from every tool.

FCKEditor.tag has been rewritten to use the new syntax.

b) get a FCKEditor internal file manager by a Connector from the jar

The new CKEditor does not provide a file manager - the license became

commercial and the whole thing became a separate project, CKFinder.

There were alternatives suggested on the web:

jasfinder - http://sourceforge.net/projects/jasfinder/support

kcfinder - http://kcfinder.sunhater.com/

some other - http://www.miguelmanchego.com/2009/gestor-de-archivos-ckeditor/

but we have already nicely integrated with the old file manager. This page:

http://jacek-kromski.jogger.pl/2009/09/25/integracja-ckeditor-z-przegladarka-plikow-z-fckeditor/

in polish says how to use the file manager from the old FCKEditor.

The steps that have to be done:

- download the new CKEditor

- download the old FCKEditor

- copy the filemanager to ckeditor directory

- in the file browser/default/frmresourceslist.html, line 92 (with SetUrl call) needs to be replaced to:

window.top.opener.CKEDITOR.tools.callFunction( window.top.document.CKEditorFuncNum, fileUrl, '' );

- in the file browser/default/browser.html add in line 80:

document.CKEditorFuncNum = GetUrlParam( 'CKEditorFuncNum');

FCKeditor has been used in version 2.6.6, the last one before switching to CKEditor project.

Changes required to use newer version of Java Integration library

for FCKEditor so it was upgraded to the latest (for FCKEditor, because one for CKEditor does not exist) version 2.6.

This also required the Prototype to be upgraded to the latest 1.6.1.

The CKEditor code also needed to be changed, so if another upgrade to a newer version occurs, we need to remember to repeat these steps:

http://cksource.com/forums/viewtopic.php?f=5&t=15750

It says:

/ckeditor/plugins/link/dialogs/link.js

Changes

label:a.lang.common.target,'default':'notSet' --> label:a.lang.common.target,'default':'_blank'

label:a.lang.link.targetFrameName,'default':'' --> label:a.lang.link.targetFrameName,'default':'_blank'

It is also worth mentioning that if you include the ckeditor.js file twice in the same page, sometimes it causes trouble, thus detection in the CKEditor.tag files.

  1. … 1096 more files in changeset.
LDEV-2372 modified ant builds to support Selenium tests

also added selenium server port property to common.properties

  1. … 4 more files in changeset.
Merge lams2_3 to head (including things not merged last time due to eclipse's merge wizard not handling the lams2_3 start point as expected)

  1. … 214 more files in changeset.
Merge lams2_3_jboss5 changes into lams2_3

  1. … 57 more files in changeset.
LDEV-2071: Added initial version of LAMS 2.3 on JBoss 5.1.

  1. … 10 more files in changeset.
LDEV-2080: For Forum tool - changed the way Hibernate properties are declared and added mapping to the missing file.

  1. … 2 more files in changeset.
LDEV-1606: Deploying classes both in tool's JAR and WAR files led to duplicate imports while trying to make Core Session Facory to be aware of tools' classes. Classes are not deployed in WAR files anymore, since they are not needed. Core Session Factory gets mappings of all the deployed tools.

  1. … 16 more files in changeset.
LDEV-1916 adding autopatch to tools, including db_version_insert.sql script to tool deployer

  1. … 71 more files in changeset.
LI-161: Generate special version of deploy.xml for tools that has a generic parameter in the place of the drive paths. This is turned on in common.properties (generate for installer) in lams_build. Only use this option if you are writing an installer/updater.

  1. … 11 more files in changeset.
Merging 2.0.1 changes from the HEAD

  1. … 244 more files in changeset.
All tools their update script to the deploy dir when the creat-tool-package task is called

  1. … 10 more files in changeset.
adding a minServerversionNumber field to deploy.xml when create-tool-package is called for all tools

  1. … 11 more files in changeset.
Added in a flag hideTool in all the tool's build.properties

  1. … 21 more files in changeset.
Fixed problem which arose when deploy-tools is called. The generated deploy.xml was pointing to the wrong sql scripts, the problem originated in the build.xml of the tools, now fixed

my bad

  1. … 11 more files in changeset.
Changing the tool's build.xml to copy the .jar and .war to the build/deploy folder, and updates the deploy.xml to point to these files

  1. … 10 more files in changeset.
Changing the build.xml of all the tools so the generated deploy.xml points to the sql scripts in the build/deploy/sql folder instead of the db/sql folder

  1. … 11 more files in changeset.
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

  1. … 2 more files in changeset.
Changing build.xml "deploy-tool" target to separate the compilation and deploy processess. This will be used later for debian packaging

  1. … 2 more files in changeset.
Added "copy-tags" to the build to make it easier to update the tags.

Updated the jsp pages to support stripes and the separate learner stylesheet.

  1. … 270 more files in changeset.