Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-3275: Deploy XML Commons as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy WDDX as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy URLRewrite as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Struts as a WildFly module.

  1. … 7 more files in changeset.
LDEV-3275: Deploy Spring as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Reload as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Quartz as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Lucene as a WildFly module. If the 3.6.2 version delivered with WildFly is used, code changes are required as API is not the same. So current version 2.4.0 is left.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Gson as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Joid as a WildFly module.

  1. … 1 more file in changeset.
LDEV-3275: Deploy Joid as a WildFly module.

  1. … 1 more file in changeset.
LDEV-3275: Deploy Jdom as a WildFly module. If the 1.1.2 version delivered with WildFly is used, code changes are required as API is not the same. So current version 0.7 is left. Same situation is with Quartz. Upgrading 1.5.3 -> 2.2.1 requires code changes.

  1. … 2 more files in changeset.
LDEV-3275: Deploy JBoss Web Server as a WildFly module. This is a fragile part as JBoss Web Server was a base for previous JBoss Application Server versions. Not it is Undertow so the Web Server is used here as a plain library for SSO valve and JSON code.

  1. … 2 more files in changeset.
LDEV-3275: Deploy JBoss Cache and Groups as a WildFly module.

  1. … 4 more files in changeset.
LDEV-3275: Deploy Apache Commons Validator as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Apache Commons HTTPClient as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Deploy Apache Commons FileUpload as a WildFly module.

  1. … 2 more files in changeset.
LDEV-3275: Use Apache Commons Pool version 1.5.1 -> 1.6 delivered with WildFly.

LDEV-3275: Use Apache Commons Codec version 1.3 -> 1.9 delivered with WildFly.

  1. … 9 more files in changeset.
LDEV-3275: Use Apache Commons Lang version 2.6 delivered with WildFly.

  1. … 38 more files in changeset.
LDEV-3275: Use Apache Commons IO version 2.1 -> 2.4 delivered with WildFly. Previous similar upgrades were: Apache Commons Collections 3.1 -> 3.2.1 Apache Commons BeanUtils 1.6 -> 1.8.3 Saaj 1.2 -> 1.3 JaxRPC same version, but delivered with WildFly.

  1. … 111 more files in changeset.
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.

    • -0
    • +83
    ./jboss-deployment-structure.xml
  1. … 38 more files in changeset.
LDEV-3275: Make application.xml use version 6 of XSD.

  1. … 1 more file in changeset.
LDEV-3275: WildFly docs state: "If you modify the MANIFEST.MF file, make sure to include a newline character at the end of the file."

LDEV-3275: Start replacing JBoss libraries with ones from WildFly. Minor changes in config files.

  1. … 37 more files in changeset.
LDEV-3275: Rename lams.application.xml to application.xml as there is no more RAMS project.

LDEV-2912: Remove RAMS remainings from source code

LDEV-2847: Number of optional LAMS EAR modules grow and making a full-text placeholder for each of them in application.xml became an issue. A new approach with short token replaced with module activation entry was used.

  1. … 3 more files in changeset.
LDEV-2905 Integrated lams_signup to LAMS core

  1. … 28 more files in changeset.
LDEV-2901, LDEV-2902: Move classes generated by Eclipse to different directory than Ant generated ones so they do not overlap and product errors.

Classpath in JAR/WAR manifests is not needed as JBoss Classloader takes care of dependencies. Manfiest was moved to a central location and is customised only with product name and version during JAR/WAR build.

  1. … 109 more files in changeset.