Well the Maven build shouldn’t care at all as the output path is always set in
the build and it’s never built using the CWD as for a maven multi-module build
is always the directory where the build was started (so in case of a
multi-module build it could be some directory other than the current
I don't think we have to keep things the way they are, but I know that
using current directory would definitely mess me up because I'm used to
the way MXMLC works.
In a brief check of compilers, javac, tsc and the regular MXMLC all
default to placing the compiled file next to the source file. Fal
MXMLFlexJSPublisher contains the following code that is run when no output
path is specified in the compiler options:
//begin code
String mainClassFolder = configuration.getTargetFileDirectory();
if (mainClassFolder.endsWith("src"))
outputParentFolder = new
File(configuration.getTargetFileDire
