Add new Dandelion profiles

[tduchateau]

... in order to address the problematics of different environments (dev, qa, prod).

Requirements

It should be possible to declare multiple locations for each asset of a bundle. For example:

{
   "bundle" : "jquery",
   "assets": [{
      "name": "jquery",
      "version": "1.11.0",
      "type": "js",
      "locations": {
         "cdn" : "//cdnjs.cloudflare.com/ajax/libs/jquery/1.11.0/jquery.js",
         "webapp" : "/assets/js/jquery.js"
      }
   }]
}

Profile definition

Then, for each different profile, a properties file will be needed.
For example :

src
|__ main
     |__ config
          |__ dandelion
               |__ dandelion.properties <== dev profile
               |__ dandelion_qa.properties <== QA profile
               |__ dandelion_prod.properties <== prod profile

Naming scheme: dandelion_[profileName].properties

In each profile, it will be possible :

• to select the selection strategy of asset locations

asset.locations.selection.strategy = cdn,jar,webjar,webapp

In this example, the cdn location will be picked up as a priority if it exists in the asset definition, then jar, etc.
Dandelion must log if none of the locations declared in the above property is mentioned in the asset definition.

• to define the same options as today

asset.minification = true
asset.processors = cssurlrewriting,jsmin,cssmin

• and custom variables, in order to be able to perform variables substitution in the bundles

MEDIA.SERVER=https://my.media.server/

As a consequence, it will be possible to declare the following kind of asset location:

{
   "bundle" : "jquery",
   "assets": [{
      "name": "jquery",
      "version": "1.11.0",
      "type": "js",
      "locations": {
         "remote" : "%MEDIA.SERVER%/libs/jquery/jquery.js",
         "webapp" : "/assets/js/jquery.js"
      }
   }]
}

Syntax: %VARIABLE% will be used instead of ${VARIABLE} in order to avoid any conflict with Maven or any other build tool that use ${} to perform resource filtering.

Profile activation

The activation of a profile will be done using the following system property :
-Ddandelion.profile.active=prod

Once the profile is retrieved at initialization, the right properties file will be loaded, i.e. dandelion_prod.properties in the example.

The profile name must be case-insensitive.
Only one profile can be activated at a time.