Brett, here are some answers that I hope will be helpful.
> 2. With the fork option set to true can I still use relative paths or
> do I need to use full paths?
You can use relative paths. Relative paths in arguments to the java
program will be relative to the "dir" attribute of the <java> task,
while relative paths in attributes of the <java> task itself (like the
jar file path) are relative to wherever Ant is running.
> 3. Here are some questions with regards to your suggested parameter
> and my assumptions as to what they should point be:
>
> * jar=${flex.mxmlc.jar}
> - Should be a relative path to the mxmlc.jar file (i.e.
> webapp/MyApplication/WEB-INF/flex/jars/mxmlc.jar)
Correct. It needn't be relative, but if it is, it will be relative to
Ant's current directory.
> * dir=${app.dir}
> - I'm not sure what this should point to. Should this be my current
> working directory or root context to my web application?
In my example, it is the doc root of the web application. This is the
working directory for the Java process in which MXMLC runs.
> * ${flex.dist.lib}
> - I assume this points to the Flex jars directory (i.e.
> webapp/MyApplication/WEB-INF/flex/jars)
*** Nope, that has to point to the lib/ directory in your Flex 1.5
distribution. (e.g. C:\Program Files\Macromedia\Flex\lib). This is
probably your current problem.
> * webroot
> - I assume this should point to the root directory of my web application.
Correct.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
