rhalferty
14 years agoNew Contributor
Environment Variable in Resource Root
To whom it concerns:
Is it possible to use an Environment Variable in Resource Root? I'm trying things like ${#ENV#PROPERTY_NAME} and ${env.PROPERTY_NAME}
We have several wsdls for our project. What I'm trying to do Is create a resource root that doesn't have to change when a user loads the project. In our build process we have all the wsdls and schemas in one place. So I'd like to reuse this PROPERTY_NAME property from our build script and use it as our resource root.
The problem occurs because some people have Windows and other Unix, so I don't want to set it to C:\wsdl and have others need /wsdl or vice-versa
Thanks
Is it possible to use an Environment Variable in Resource Root? I'm trying things like ${#ENV#PROPERTY_NAME} and ${env.PROPERTY_NAME}
We have several wsdls for our project. What I'm trying to do Is create a resource root that doesn't have to change when a user loads the project. In our build process we have all the wsdls and schemas in one place. So I'd like to reuse this PROPERTY_NAME property from our build script and use it as our resource root.
The problem occurs because some people have Windows and other Unix, so I don't want to set it to C:\wsdl and have others need /wsdl or vice-versa
Thanks