build.properties

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-5433 Squash DB patches and update versions

  1. … 107 more files in changeset.
LDEV-5328 Set proper initial tool version so SQL scripts can kick in

  1. … 24 more files in changeset.
LDEV-5328 Squash DB patches and update versions

  1. … 154 more files in changeset.
Merge branch 'LDEV-4979' into LDEV-4951

# Conflicts:

# lams_tool_assessment/src/java/org/lamsfoundation/lams/tool/assessment/service/AssessmentServiceImpl.java

# lams_tool_assessment/src/java/org/lamsfoundation/lams/tool/assessment/service/IAssessmentService.java

# lams_tool_lamc/build.properties

# lams_tool_lamc/db/sql/create_lams_tool_mc.sql

# lams_tool_lamc/db/sql/tool_insert.sql

# lams_tool_lamc/src/java/org/lamsfoundation/lams/tool/mc/dao/hibernate/McUserDAO.java

# lams_tool_lamc/src/java/org/lamsfoundation/lams/tool/mc/service/IMcService.java

# lams_tool_lamc/src/java/org/lamsfoundation/lams/tool/mc/service/McService.java

# lams_tool_lamc/src/java/org/lamsfoundation/lams/tool/mc/web/controller/MonitoringController.java

# lams_tool_lamc/web/403.jsp

# lams_tool_lamc/web/404.jsp

# lams_tool_lamc/web/WEB-INF/web.xml

# lams_tool_lamc/web/common/taglibs.jsp

# lams_tool_lamc/web/error.jsp

# lams_tool_lamc/web/login.jsp

  1. … 6 more files in changeset.
LDEV-4979 Update SQL scripts for LAMS 4.0 release

1. Update SQL scripts (create_lams_tool_*.sql), to avoid running 3.1 to

4.0 autopatch scripts on every build.

2. Update module version to 20200219 in build.properties.

3. Squash patches that upgrade from 3.1 to 4.0 into a single one.

  1. … 58 more files in changeset.
LDEV-4951 Remove traces of MCQ tool from other modules

  1. … 192 more files in changeset.
LDEV-4743 Squash/Update SQL scripts ready for LAMS 3.1 release

  1. … 129 more files in changeset.
LDEV-4721 Revert initial tool version

Tool version should be bumped only when previous patches have been

merged into build scripts. This was not such situation. We should keep

old tool version and allow patches to execute.

  1. … 4 more files in changeset.
LDEV-4721 Add class renaming filter for tool content import

  1. … 17 more files in changeset.
LDEV-4180: Remove obsolete properties.

  1. … 6 more files in changeset.
LDEV-4180: Make DB patches produce up-to-date structure during build instead of applying multiple patches. Get rid of unnecessary tables and keys. Modify boolean columns to tinyint(1) Simplify patches where possible.

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

  1. … 1313 more files in changeset.
LDEV-2839: Allow JSP precompilation in Multiple Choice Tool.

  1. … 1 more file in changeset.
LDEV-2657 Date restrictions for MCQ (merge to HEAD)

  1. … 17 more files in changeset.
LDEV-1998: Committing Pedagogical Planner base files and support for chat, forum, multiple choice, Q&A, noticeboard, notebook and vote tools.

  1. … 111 more files in changeset.
Preparing for new release of tool - version number to be 20070820

  1. … 1 more file in changeset.
Updated minimum version number and tool version for 2.0.3 release. Tool contract change occured in this release.

  1. … 10 more files in changeset.
Merging RAMS and Edit On Fly changes from branch to the head.

  1. … 239 more files in changeset.
added in a property to each tool's buiild.properties for the language packe package

  1. … 12 more files in changeset.
Changed the tool_version to 20070214 for qa, mc, vote and nb

  1. … 3 more files in changeset.
Changing the minimum server version number in all the tool's build.xml to 2.0.200612051427, (lams-2.0)

  1. … 11 more files in changeset.
added an entry to all the tool's build.xml for minServerVersionNumber to be put in the deploy.xml

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

  1. … 21 more files in changeset.
LDEV-1146: Increase login field length to 255.

  1. … 4 more files in changeset.
Changes made to all tools, so they should be made in the example tool

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. … 7 more files in changeset.
*** empty log message ***

  1. … 1 more file in changeset.
*** empty log message ***

  1. … 6 more files in changeset.
*** empty log message ***

  1. … 15 more files in changeset.
Multiple ChoiceTool 1.1 initial setup

  1. … 167 more files in changeset.