lams-github / lams_build

deploy-tool

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
Tuesday 21 Jun 2005
7:55 am

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
    ./lib/lams-tool-deploy.jar
Wednesday 15 Jun 2005
7:06 am

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
    ./lib/commons-collections.jar
    • binary
    ./lib/commons-configuration-1.1.jar
    • binary
    ./lib/commons-dbutils-1.0.jar
    • binary
    ./lib/commons-io-1.0.jar
    • binary
    ./lib/commons-lang-2.0.jar
    • binary
    ./lib/commons-logging.jar
    • binary
    ./lib/lams-tool-deploy.jar
    • binary
    ./lib/mysql-connector-java-3.1.7-bin.jar
  9. … 4 more files in changeset.
7:00 am

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
    • -0
    • +1
    ./deploy.bat
    • -0
    • +4
    ./deploy.sh
  3. … 1 more file in changeset.