lams / lams_tool_example

build.xml

Tools

Line History

Line Count Graph
Line Count Graph

Stats

Commits this week: 0
Total Committers: 3
Last Commit: 27 Mar 12
Commits this week: 0
Total Lines of Code (LoC): 545
Net change in LoC this week: 0

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 27 Mar 2012
6:37 pm

Marcin Cieslak

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

Options
    • -5
    • +2
    ./build.xml
  2. … 26 more files in changeset.
6:25 pm

Marcin Cieslak

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.

Options
    • -5
    • +3
    ./build.xml
  2. … 26 more files in changeset.
Friday 23 Mar 2012
6:44 pm

Marcin Cieslak

LDEV-2839: Allow JSP precompilation in Example Tool.

Options
    • -27
    • +122
    ./build.xml
  2. … 1 more file in changeset.
Tuesday 06 Mar 2012
7:15 pm

Marcin Cieslak

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.

Options
    • -20
    • +20
    ./build.xml
  2. … 50 more files in changeset.
Thursday 15 Feb 2007
12:47 pm

lfoxton

All tools their update script to the deploy dir when the creat-tool-package task is called

Options
    • -7
    • +13
    ./build.xml
  2. … 10 more files in changeset.
9:12 am

lfoxton

adding a minServerversionNumber field to deploy.xml when create-tool-package is called for all tools

Options
    • -0
    • +1
    ./build.xml
  2. … 11 more files in changeset.
8:16 am

lfoxton

Added in a flag hideTool in all the tool's build.properties

Options
    • -0
    • +2
    ./build.xml
  2. … 21 more files in changeset.
Wednesday 14 Feb 2007
10:05 am

lfoxton

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

Options
    • -2
    • +2
    ./build.xml
  2. … 11 more files in changeset.
Tuesday 13 Feb 2007
2:26 pm

lfoxton

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

Options
    • -2
    • +9
    ./build.xml
  2. … 10 more files in changeset.
1:27 pm

lfoxton

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

Options
    • -6
    • +6
    ./build.xml
  2. … 11 more files in changeset.
8:57 am

lfoxton

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

Options
    • -0
    • +1
    ./build.xml
  2. … 5 more files in changeset.
8:53 am

lfoxton

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

Options
    • -1
    • +9
    ./build.xml
  2. … 3 more files in changeset.
Friday 09 Feb 2007
9:56 am

lfoxton

(This was changed in all the other tools, so should also be changed for the example tool) Changing build.xml "deploy-tool" target to separate the compilation and deploy processess. This will be used later for debian packaging

Options
    • -2
    • +5
    ./build.xml
Sunday 17 Sep 2006
2:19 pm

fmalikoff

Updated address of FSF in copyright statement

Options
    • -2
    • +2
    ./build.xml
  2. … 795 more files in changeset.
Friday 14 Apr 2006
2:31 pm

fmalikoff

Tool deployment utility has been changed to update the context path and class path when the tool is deployed. Build file changed to match and the main tool context application file moved so that only the tool's have a context file classpath of /org/lamsfoundation/lams/tool.

Options
    • -0
    • +2
    ./build.xml
  2. … 26 more files in changeset.
Wednesday 05 Apr 2006
11:15 am

fmalikoff

Added LAMS custom tags directory

Options
    • -0
    • +1
    ./build.xml
  2. … 5 more files in changeset.
Tuesday 28 Mar 2006
6:21 am

fmalikoff

Moved the language/message/resource file to the conf area. Will now be deployed to the lams-dictonary.jar to make I8N easier.

Options
    • -15
    • +12
    ./build.xml
  2. … 49 more files in changeset.
Wednesday 22 Mar 2006
10:12 am

fmalikoff

Implemented some basic Hibernate POJOs and their DAOs, along with an applicationContext.xml file. The tool should now deploy okay and appear in authoring. So you can run a lesson with it but you can't actually do anything as the service doesn't store any data and no jsp pages exist.

Options
    • -61
    • +0
    ./build.xml
  2. … 30 more files in changeset.
Tuesday 21 Mar 2006
12:34 pm

fmalikoff

Initial version of example tool. DB setup done but Hibernate objects are yet to be done.

Options
    • -0
    • +488
    ./build.xml
  2. … 44 more files in changeset.