Profile Reference

Note: This pages needs review and may not be up to date

Here we are adding the description of the existing profiles

• We have included several profiles for the client side in the parent POMs. For OSGI bundles that have javascript we created the following profiles:
  • In pentaho-parent-pom
    • javascript-require-cfg
      • This profile is used for the aggregation of require.cfg dependencies
    • node-npm
      • Active when there exists a javascript configuration folder
      • Locally installs node and npm
      • Unzips javascript dependencies based in the list of javascript dependency names (artifact Ids declared in the POM) from the ${js.project.list} variable. These dependencies are usually used for tests or for assembly.
    • javascript
      • does the “traditional” requireJs build
    • javascript-test
      • This profile is active if a javascript test src folder exists ( conventioned to be src/test/javascript )
      • Sets up the test environment based on the package.json file located in ${frontend-maven-plugin.workingDirectory}. This property value is computed to use the highest base dir of the project.
      • This profile makes the assumption that the package.json file, properly configured, exists at the highest base dir the project.
      • Runs the javascript unit tests with karma based on karma configuration file in ${build.javascriptTestConfigDirectory}/${karma.file.config}. This is conventioned to be src/test/config/javascript / karma.ci.conf.js.
    • js-doc
      • Generates the API reference documentation for javascript using js-doc notation.
      • Is activated based on the existence of ${basedir}/src/doc/javascript/config/${docjs.config.file}
  • In pentaho-ce-bundle-parent-pom
    • bundle-javascript
      • This profile makes the assumption that a js build file exists in the javascript osgi configuration folder ${build.javascriptConfigDirectory}/osgi/${requirejs.build.file}. It is defined as src/main/config/javascript/osgi/build.js
      • Executes the rjs build with a set unchangeable configurations. Marks the javascript output directory as a resource in order for it to be included in the resulting osgi bundle. The unchangeable configurations are:
        • Code is uglified, Source maps are generated and included in the artifact and comments are removed.