lams-github / lams_build / lib / autopatch

autopatch.module.xml

Clone Tools

Stats

Commits this week: 0
Total Committers: 1
Last Commit: 09 Oct 14
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
Thursday 09 Oct 2014
5:55 pm

Marcin Cieslak

LDEV-3319: Synchronize patch execution with an external monitor. Modules in WildFly can be loaded in parallel. AutoPatch is not ready for this as it uses static methods with unsynchronized collections. Each AutoPatchService instance should be run sequentially.

Options
    • -41
    • +0
    ./autopatch.module.xml
  2. … 32 more files in changeset.
Thursday 28 Aug 2014
7:39 pm

Marcin Cieslak

LDEV-3275: Add library dependencies and source code.

Options
    • -1
    • +8
    ./autopatch.module.xml
  2. … 415 more files in changeset.
Tuesday 05 Aug 2014
9:47 pm

Marcin Cieslak

LDEV-3275: Set module dependencies.

Options
    • -0
    • +4
    ./autopatch.module.xml
  2. … 7 more files in changeset.
Friday 01 Aug 2014
4:59 pm

Marcin Cieslak

LDEV-3275: Deploy EAR libraries as WildFly modules. In JBoss there were several folders where libraries could be simply copied. In WildFly it is more organised, with module.xml files describing each library. In order not to keep libs in EAR, so only real LAMS code remains there, they are moved to WildFly as modules and get referenced by EAR with META-INF/jboss-deployment-structure.xml.

Options
    • -0
    • +30
    ./autopatch.module.xml
  2. … 38 more files in changeset.