I try to avoid setting real environment variables since I find it more convenient to use the properties files to remember all of the values for later. For instance, I added approvefalcon.properties to set env.ANT_HOME. However, it looks like the values from approvefalcon.properties don't get inherited by other Ant scripts started by ApproveFalcon.xml, so I guess I need to set real environment variables this time.
- Josh On Fri, Nov 13, 2015 at 12:11 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/13/15, 12:06 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: > > >I discovered that ant in /opt/local/bin was actually a symlink to the real > >location inside the bin directory of /opt/local/share/java/apache-ant, > >which I think is the default ant on OSX. > >/opt/local/share/java/apache-ant/lib is still not writable without > >privilege escalation, for some reason, but at least the surrounding files > >look more appropriate for a full installation of Ant. > > Hmm. I wonder how folks are supposed to add new jars to their Ant > installs. I guess it may be safer to install it in the test folder and > try to reference it from the script. > > > > >I've almost made it through now, I think. I just need to get all of the > >environment variables correct for the unit tests. > > Which environment variables are still giving you problems? > > -Alex > >
