24 Sep, 2015

3 commits


23 Sep, 2015

12 commits


22 Sep, 2015

5 commits


21 Sep, 2015

3 commits


18 Sep, 2015

5 commits


17 Sep, 2015

4 commits


16 Sep, 2015

4 commits


15 Sep, 2015

3 commits

  • A JavaScript build process is more manageable and is compatible
    with far more JavaScript tooling than the existing Maven process.
    As an added benefit, Node.js executes the build an order of magnitude
    faster than the Java-based Rhino runtime.
    
    In order to provide a version of Node.js for the JavaScript build
    to use, this change introduces the use of frontend-maven-plugin, which
    downloads and executes Node.js.
    
    Maven is currently still responsible for the unpacking of the
    project dependencies and the packaging of the final artefact.
    
    The only change in behaviour in this change is the replacement of
    JSLint with ESLint. This is because the version of JSLint used by
    the Maven build was 2011-03-07, which is not supported by the
    grunt wrapper.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@15708 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    joe.bandenburg
     
  • git-svn-id: https://svn.forgerock.org/openam/trunk@15705 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    hshabuldayeva
     
  • git-svn-id: https://svn.forgerock.org/openam/trunk@15699 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    phil.ostler
     

14 Sep, 2015

1 commit

  • By using a JavaScript module, we give the user more flexibilty in
    defining their theming config. It also allows us to include comments
    to act as documentation and to provide a simpler syntax for
    regular expressions (as these can be written inline in JavaScript).
    
    This change also includes significant refactoring of the
    ThemeManager to simplify it.
    
    git-svn-id: https://svn.forgerock.org/openam/trunk@15692 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
    joe.bandenburg