You are right, not everything could be configured in JNDI. The logger
is a good example. For web application packaged as WAR, you can define
separate project module, and apply the overlay with logger
configuration.
<!-- Customize artifact before deployment -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<overlays>
<overlay>
<groupId>${project.groupId}</groupId>
<artifactId>modular-war-webapp</artifactId>
</overlay>
</overlays>
</configuration>
</plugin>
For more complete example, please look into
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-deploy/pom.xml
Not ideal, but much better than profiles in the web application
module. The deployment specific configuration is located in separate
"deploy" module.
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
On 27 July 2011 15:43, Daniel Serodio (lists) <daniel.lis...@xxx.com.br> wrote:
> Ansgar Konermann wrote:
>>
>> Am 25.07.2011 22:13, schrieb Daniel Serodio (lists):
>>>
>>> Do you think using a classifier to differentiate artifacts built for
>>> development and production is "hacky", is is this an appropriate
>>> solution?
>>
>> Use the same *artifacts* for all stages and allow for *configuring* the
>> relevant properties of your application at runtime/startup time, as much
>> as possible.
>>
>> A common mechanism to configure things at runtime is using JNDI
>> parameters.
>
> I'mconsidering changing our build process. Setting up the DB using JNDI is
> easy enough, but how do you suggest we deal with different logging
> configurations, which differ not only on some values, but structure (ie
> log4j Loggers and Appenders with different classes, file paths and severity
> thresholds) ?
>
> Regards,
> Daniel Serodio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
