lams-github / lams_build / deploy-tool

lib

Clone Tools

Stats

Commits this week: 0
Total Committers: 9
Last Commit:
Commits this week: 0

Lines of code count not available

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
Wednesday 14 Feb 2007
10:33 am

lfoxton

Tool-deployer upgrade, checks the db for tool_signature and tool_version, stops if current tool is up to date, installs entire tool if the signature is not present in the db

TODO: update db and jar and war files if tool exists, but is not the newest version

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 4 more files in changeset.
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
    • binary
    ./lams-tool-deploy.jar
  2. … 11 more files in changeset.
Tuesday 13 Feb 2007
8:28 am

lfoxton

lams-tool_deploy generates a tool_version entry for a tool's deploy.xml

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 3 more files in changeset.
Monday 03 Jul 2006
8:18 am

fmalikoff

Added styling images to export portfolio. This required making lams-central.war an expanded war and adding the lams directory to the configuration file so that the css and image files could be copied using a file copy rather than using http (for performance).

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 6 more files in changeset.
Friday 14 Apr 2006
2:44 pm

fmalikoff

Tool deployment utility has been changed to update the context path and class path when the tool is deployed.

Options
    • binary
    ./lams-tool-deploy.jar
Wednesday 29 Mar 2006
7:20 am

fmalikoff

Completed linking of a language file to a complex activity. The last check in of code was missing setting the language file in the database - it only copied the file.

On doing this second part, I found that I hadn't passed data around in the same manner as Chris originally designed. So I removed the Maps returned by the tasks and went over to Chris' way of just calling the tasks to get any necessary cross-task information.

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 20 more files in changeset.
Tuesday 28 Mar 2006
3:53 pm

fmalikoff

Updated Tool Deployer so that that parallel activities, installed using the tool deployer, can also be I18N.

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 6 more files in changeset.
Monday 27 Mar 2006
11:30 am

fmalikoff

Added greater flexibility to the language files for the tool deployment - the deployment configuration now specfies the package into which the file(s) shoul be placed. For tools this may be their normal package, or a tool signature directory. For non-tool activities this will be a artificial name.

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 4 more files in changeset.
Friday 17 Mar 2006
6:44 am

fmalikoff

Updated mysql-connector, to go with MySQL 5.0

Options
    • binary
    ./mysql-connector-java-3.1.12-bin.jar
    • binary
    ./mysql-connector-java-3.1.7-bin.jar
  3. … 2 more files in changeset.
Friday 10 Mar 2006
2:18 pm

fmalikoff

Copies specified language files from tool directories to the lams-dictionary.jar in the ear. Added a fileset to the ant tag - couldn't do it as nicely as I would have wanted as I couldn't get nested tags working.

Options
    • binary
    ./lams-tool-deploy.jar
  2. … 19 more files in changeset.
Friday 02 Dec 2005
8:51 am

mtruong

*** empty log message ***

Options
    • binary
    ./lams-tool-deploy.jar
    • binary
    ./xstream-1.1.2.jar
Tuesday 21 Jun 2005
1:55 pm

fmalikoff

If the lams_tool record doesn't exist, doesn't try to delete the lams_blah table entries or the tool's own tables.

Options
    • binary
    ./lams-tool-deploy.jar
Wednesday 15 Jun 2005
1:06 pm

fmalikoff

Setup tool_deploy so that it can be built and loaded into lams_build project, the properties file generated from a build script and the deployment run from a built script. This was done to make a usuable development tool deploy task as well as make it easier to build the deployment package.

Options
    • binary
    ./commons-collections.jar
    • binary
    ./commons-configuration-1.1.jar
    • binary
    ./commons-dbutils-1.0.jar
    • binary
    ./commons-io-1.0.jar
    • binary
    ./commons-lang-2.0.jar
    • binary
    ./commons-logging.jar
    • binary
    ./lams-tool-deploy.jar
    • binary
    ./mysql-connector-java-3.1.7-bin.jar
  9. … 4 more files in changeset.