compiler config file is not used

[GoogleCodeExporter]

What steps will reproduce the problem?

1. use standard flex mojo setting with a compiler config.xml under resources 
folder.
2. to be sure use the configFile property in the build configuration
3. build a theme from a css file, where one or more swc-files (exported from 
flash) are used 
3. Run a mvn compile

What is the expected output? What do you see instead?

In our ant build we used the library-path settings to get the swc'c on the 
classpath.
We used exactly the same config for the maven build. During the compilation 
process all classes 
defined in the swc's were not found. The mojo complained about using the 
config.xml file, but 
the property had no effect - the library path was empty (is this true for all 
properties in the 
config.xml?)

What version of the product are you using? On what operating system?

flex-mojo 2.0M9 on OSX.

Please provide any additional information below.

I guess this is pretty standard stuff we are doing here. It makes no sense to 
define those flash 
swc's as dependencies in the pom. We would like to switch to maven builds, but 
have to make 
sure, that the config.xml really controls the compiler configuration. This 
seems not to be the 
case at least for the library-path and external-library-path.

Original issue reported on code.google.com by matthias...@gmail.com on 9 Jan 2009 at 11:13

[GoogleCodeExporter]

Well, most of the config.xml will be ignored by flex-mojos.  That is a technical
limitation, and doesn't appear to have any workaround to deal with that.  So I
strongly advise you to no rely on config.xml to keep your configurations.  Keep 
it on
pom.

But, even if we don't have this limitation, all dependencies should be managed 
by
maven in order to produce reproductives builds, so you do need dependencies to 
that.

If I get this right you are using themes:
there are 2 ways to define themes.
1 - The old one...
 <dependency>
   <groupId>com.acme</groupId>
   <artifactId>acme-theme</artifactId>
   <type>swc</type>
   <scope>theme</scope>
   <version>1.0</version>
 </dependency>

2 - Using themes:
 <themes>
    <theme>css/main.css</theme>
 </themes>

They can be used together.

But I'm not sure if is that what you wanna at your config.xml.  If not is that, 
can
you provide me the piece of config.xml you need on build.

Original comment by velo...@gmail.com on 10 Jan 2009 at 1:41

• Changed state: WontFix