I did some further research and found that my variable wasn't in systemScope.
Why would it be there locally on Eclipse but not the build machine. Is
there something I need to do to enable that?
I had to resort to something like this to see the variable, but that still
presents me the problem of having to hardcode the environment in my
maven.xml:
<goal name="echome" >
<echo>${runtime.env}</echo>
<echo>${systemScope.setProperty("runtime.env",'TST')}</echo>
<j:choose>
<j:when test="${systemScope['runtime.env'] == 'TST'}">
<echo>${runtime.env} is found</echo>
</j:when>
<j:when test="${runtime.env} == 'TST'">
<echo>${runtime.env} is not found</echo>
</j:when>
</j:choose>
</goal>
Please let me know if there is anyway for it to pickup my ${runtime.env}
from my project.properties on the build server.
Thanks,
Lou
lsacco wrote:
>
> I have a "runtime.env" variable in my project.properties that has the
> specific environment I want to use. Then in my maven.xml I use this
> variable in 'if' statements (note: I'm using Maven 1.0.2 so this is
> Jelly). For some reason this works fine in Eclipse, but when I run from
> CruiseControl this variable is not picked up and so my filtered @@
> variables are not being changed.
>
> Does anyone know how I can remedy this?
>
> Thanks,
> Lou
>
--
View this message in context:
http://www.nabble.com/project.properties-property-not-being-picked-up-tf3417665s177.html#a9560347
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
