Have standalone module poms for Flex SDK

[GoogleCodeExporter]

What steps will reproduce the problem?
1. You can't use the super-poms, but need dependencies to Flex SDK
2. You have to add a whole page of dependencies for a flex-mojos build to work

What is the expected output? What do you see instead?
You should be able to add a dependency to the Flex SDK with a single dependency 
in your pom. 
There should probably be different poms for the SDK, a base one, one with 
charts, one with 
automation, or maybe just a basic and a full, where the full includes all the 
automation and charts 
stuff.

That would also make it easier to handle different Flex SDK versions easily.

Original issue reported on code.google.com by RedB...@gmail.com on 17 Jul 2008 at 7:50

[GoogleCodeExporter]

Agreed.  We already have a parent pom reference, so we cannot use the flex 
super pom
as a parent.

Original comment by codebene...@gmail.com on 26 Aug 2008 at 6:58

[GoogleCodeExporter]

Looks like this issue is already resolved.

If you install the flex sdk using the installer-mojo then all you need in your 
pom or
parent pom is:
<dependency>
   <groupId>com.adobe.flex</groupId>
   <artifactId>compiler</artifactId>
   <version>3.1.0.2710</version>
   <type>pom</type>
</dependency>
<dependency>
   <groupId>com.adobe.flex.framework</groupId>
   <artifactId>flex-framework</artifactId>
   <version>3.1.0.2710</version>
   <type>pom</type>
</dependency>

Original comment by llin...@gmail.com on 26 Sep 2008 at 6:52

[GoogleCodeExporter]

Good point.

Original comment by velo...@gmail.com on 26 Sep 2008 at 7:14

• Changed state: Fixed