Web Applications
How to configure Maven to manage a multi branded web applications (that uses Wicket) and keep the development environment comfortable.
In this second part, I will address how Wicket handles the branded configuration and how to make the development environment "brand-friendly".
Tools
How to configure Maven to manage a multi branded web applications (that uses Wicket) and keep the development environment comfortable.
In this second part, I will address how Wicket handles the branded configuration and how to make the development environment "brand-friendly".
In this two part article, I will explain how to configure a web application built with Maven to support "branding", or skinning. That is, support different distribution skinned with particular images, logo, background, text. In the end we just want to keep separated the static contents and choose the right set when we package our application so that the result is a war with just the content for a single company. I call this a branded distribution using brand as a similar work for skinning. Brand looks more enterprise and general than skinning, anyway :) In the second part of the article I will also cover the Wicket side of the story. The Maven side works by himself, anyway.
read the complete article
Deployment
In this two part article, I will explain how to configure a web application built with Maven to support "branding", or skinning. That is, support different distribution skinned with particular images, logo, background, text. In the end we just want to keep separated the static contents and choose the right set when we package our application so that the result is a war with just the content for a single company. I call this a branded distribution using brand as a similar work for skinning. Brand looks more enterprise and general than skinning, anyway :) In the second part of the article I will also cover the Wicket side of the story. The Maven side works by himself, anyway.
read the complete article
