In general, try to avoid using env vars as it makes your build more fragile
as you¹ve noticed. Somehow it seems these env aren¹t getting through to
maven, but there¹s not enough info below to tell you why.
On 4/2/09 6:46 AM, "amys" <amy.t.sav...@gmail.com> wrote:
>
>
> I use an environment variable like ${env.FLORENCE_HOME} in my pom.xml files.
> Sometimes this resolves correctly, sometimes it doesn't, and then Maven
> generates files into a directory literally called ${env.FLORENCE_HOME} in
> my build environment.
>
> Specifically, I define a variable ${florence.server} based on
> ${env.FLORENCE_HOME} in one pom.xml, then reference ${florence.server} in
> another pom.xml.
>
> This generally works, and I cannot tell what triggers the problem, Moreover,
> even where the bug occurs, the base pom is being correctly referenced, as
> the variable ${florence.server} does resolve, even when the env variable it
> references does not.
>
> Using
> - Maven 2.1
> - Eclipse Maven Plugin 0.9.7 of 20081130
> --
> View this message in context:
> http://www.nabble.com/Maven2-ignoring-environment-variables-tp22845174p2284517
> 4.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
