maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrien Rivard <adrien.riv...@gmail.com>
Subject Re: Default value for properties depending on active profile
Date Fri, 18 Oct 2013 08:28:34 GMT
Hi,

You should just override the context-param when deploying on the real
production server.




On Fri, Oct 18, 2013 at 9:40 AM, Martin Hoeller <martin@xss.co.at> wrote:

> Hi!
>
> Here is the short version of what I want: I've got a JEE6 webapp with a
> web.xml file, where the context-parameter facelets.DEVELOPMENT should be
> enabled in development mode but disabled for releases.
>
> My idea to solve this problem is as follows:
>
> 1) Define the context parameter in web.xml like this
>
>    <context-param>
>       <param-name>facelets.DEVELOPMENT</param-name>
>       <param-value>${devel.mode}</param-value>
>    </context-param>
>
> 2) Configure the maven-resources-plugin to filter web.xml and replace
>    ${devel.mode} with the actual value.
>
> 3) Make devel.mode a maven-property with it's value being 'true' for
>    normal builds and 'false' for a release build.
>
> My questions is, is this a recommended way or should I solve this task
> differently?
>
> If this is ok, how could I initialize devel.mode correctly? I was
> thinking about a default initialization in the pom.xml and an alternative
> initialization via the release-profile. My qualms about this approach
> are, that profiles are considered evil for most use-cases.
>
> Many thanks in advance,
> - martin
>



-- 
Adrien Rivard

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message