lams-github / lams_tool_deploy

.classpath

Clone Tools

Stats

Commits this week: 0
Total Committers: 9
Last Commit: 05 Apr 24
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
Monday 30 Jul 2012
8:55 pm

Marcin Cieslak

LDEV-2847: Major changes to build.xml files. See JIRA comment for full explanation.

Options
    • -7
    • +3
    ./.classpath
  2. … 1313 more files in changeset.
Thursday 22 Mar 2012
2:10 pm

Andrey Balan

LDEV-2829 updating Apache Commons IO lib

Options
    • -1
    • +1
    ./.classpath
Tuesday 06 Mar 2012
12:16 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
    • -9
    • +13
    ./.classpath
  2. … 50 more files in changeset.
Thursday 16 Apr 2009
10:02 am

erniegx <ernieg@gmail.com>

LDEV-2239: Upgrading mysql connector

Options
    • -1
    • +1
    ./.classpath
  2. … 19 more files in changeset.
Thursday 30 Oct 2008
4:48 am

asukkar

Updated .classpath

Removed references to lams jar files in lams_build/lib

Options
    • -0
    • +1
    ./.classpath
  2. … 22 more files in changeset.
Friday 02 Dec 2005
1:03 am

mtruong

*** empty log message ***

Options
    • -0
    • +1
    ./.classpath
Wednesday 15 Jun 2005
5:58 am

fmalikoff

Rationalised jars to match the common jar libraries, but left in project. 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
    • +17
    ./.classpath
  2. … 19 more files in changeset.