Overview

• Introduction
• Usage
• Goals
• FAQ

Advanced Usage

• Merging Applications
• Merging Applications and Webapplications
• Building RPM packages

Project Documentation

• Project Summary
• Release Notes

CoreMedia Links

• Online Documentation
• Get Help from our Support
• Contributions

• Added parameter to ignore tokens in find-filter-tokens mojo
• Added paramter in find-filter-tokens mojo to allow only tokens matching a pattern. This paramter has to be used in conjunction with failOnFoundTokens set to true.
• Fixed issue where the property file generated by find-filter-tokens mojo contains all values multiple times when no clean was done.
• Added prefix parameter to zipConfig to add a directory prefix for the zipped content.
• Switched from JarArchiver to ZipArchiver for the zip-it mojo. As a result no META-INF/MANIFEST.MF entry will be generated any more.

• Added parameter dos2unixPattern to configure the dos to unix fileending conversion
• Added flag to disable escaping of windows paths during resource filtering
• Bugfix RPM mojo - defaultuser and defaultgroup parameters did not work when no mapping was defined.

• Requires at least Maven 3.0.4
• New goal parameter
  • Added stripJarVersions parameter to package-inplace and package-webstart goals to strip the version information from the jar filenames, when retrieving jars. The stripping won't affect jars that are included in coremedia-application or zip dependencies.
  • Added excludeTransitiveJars parameter to package-inplace and package-webstart goals to exclude transitive jar dependencies from being copied to the targets lib directory.

• New artifactId to context mapping for embedded webapps To allow merging of two webapps with identical artifactId but different groupId when embedding a war dependencies into a coremedia-application, the parameter artifactIdToContextDir has been deprecated and a new parameter webapps has been added. The new parameter is a list of webapp configuration elements where groupId, artifactId, classifier and context can be specified. groupId and classifier are optional whereas artifactId and context are mandatory. The new syntax for merging a webapp may look like the following example snippet:

  <configuration>
   ...
   <webapps>
     <webapp>
       <groupId>org.change.me</groupId>
       <artifactId>some-war</artifactId>
       <classifier>test</classifier>
       <context>webapp</context>
     </webapp>
   </webapps>
   ...
   </configuration>

• find-filter-tokens mojo added This mojo parses all configuration files below the output directory for ant style filter tokens and generates a property file containing all necessary tokens for post-install configuration. The generated file can be attached to the build with packagingtype "properties" and classifier "configuration-template". The tokens can also be injected into the build of the current project with a configurable property name. The mojo can also be used to fail a build if there are still tokens found. This can be achieved if the cofiguration parameter failOnFoundTokens is set to true. With the defaultConfigurationProperties parameter you can define a property file which may contain default values for the tokens and comments to be included in the configuration-template files.

• Modification of property files added Instead of duplicating files from dependencies to change its configuration, it is now possible to add,remove or change property configuration files by simply defining the delta in a property file named exactly the same as the targeted file and placed below the same directory structure relative to a common base directory for override configuration files. E.g. if you have a property file at corem/properties/contentserver.properties and you don't want to duplicate the whole file, just to replace the host property, you can now place a property file at src/main/override-properties/properties/corem/contentserver.properties that only contain the following snippet.

  contentserver.host=my.host

Filtering is also possible, because the override config files are filtered in advance of the processing.

• Filtering of dependencies added
  • Setting <dependencyFiltering>true</dependencyFiltering> dependencies will be extracted and afterwards filtered.
  • The patterns to define the files to befiltered can be configured with

  <dependencyFilteringPattern>
    <dependencyFilteringPattern>**/*.properties</dependencyFilteringPattern>
    <dependencyFilteringPattern>**/*.xml</dependencyFilteringPattern>
  </dependencyFilteringPattern>

using the default pattern:

**/*.xml, **/*.conf, **/*.inc, **/*.sh, **/*.bat, **/*.jpif, **/*.properties, **/*.txt, **/*.bsh

• RPM goal added
  • with the new rpm goal it is possible to package native rpm packages. The goal comes with three inbuilt configurations for everything(default), coremedia-applications and tomcat servlet-containers.

• ArtifactId changed
  The maven- prefix for plugins is reserved to the core maven plugins and won't be supported for other plugins in future releases.
• Feature added
  • Check for version conflict on resource level in merge mode. To enable this feature set <checkMergedVersions>true</checkMergedVersions>

• Features added
  • Added lifecycle, packaging type and mojos to create webstart webapplications.
• Bug Fixes
  • Cleanup the documentation.

• Dependency Update Update to maven 3 API. The plugin now requires Maven 3.
• Features added
  • Added overlay feature to exclude files from coremedia-application artifact dependencies.
  • Speed up build by omitting extraction of transitive coremedia-application dependencies.
• Bug Fixes
  • Fix order applications are merged, to be the same as dependencies are defined.
  • Disable filtering of .