maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: releas:perform with profiles fails
Date Mon, 20 Dec 2010 15:24:07 GMT includes a blog entry on using 
JNDI to get environment stuff out of projects.
Got tired of writing it every week here.
Putting environmental stuff inside your modules is a recipe for long 
frustrating Maven discussions and hours of fruitless screwing about.

If you want anyone to guess as to what causes a compilation error, you 
will have to give us some hints about it.
What error?
What does Maven say is happening?

Separation of concerns between development and deployment will make both 
sides of the job much easier and much less prone to run-time screw-ups 
in production.
As you get further into the process, you will likely get a lot more 
environments to support - current production, customer acceptance 
testing, pre-release testing, integration testing, localhost testing, 
etc. If you have customization for customers or multiple releases in 
production, your problems multiply.

Get the deployment stuff out of your codebase ASAP.


On 20/12/2010 9:23 AM, Hauschel Fred Robert wrote:
> Hi list,
> I've a multi module with differences between the prod and dev
> environment. Threfor I've defined some profiles.
> "mvn clean install -P devContainerSettings,dependencies,!eclipse" works
> fine!
> but  "mvn --batch-mode release:prepare -P
> devContainerSettings,dependencies,!eclipse" fails with compilations
> errors!
> Any idea??
> Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_21
> Java home: C:\Program Files\Java\jdk1.6.0_21\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Fredy
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message