yeah, you're right. With the dependencies below, it compiles fine and the
-compiler.external-library-path are correct. This is a perfect workaround
but not very handy... But again, there is no time pressure for a better
solution.
Thanks,
Marc
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>flex</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>framework</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>framework</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>zip</type>
<classifier>configs</classifier>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>framework_textLayout</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>rpc</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>spark</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>sparkskins</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>textLayout</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>utilities</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>playerglobal</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>swc</type>
<classifier>10</classifier>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>framework</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>rb.swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>rpc</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>rb.swc</type>
</dependency>
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>spark</artifactId>
<version>4.0.0.8811</version>
<scope>external</scope>
<type>rb.swc</type>
</dependency>
On Wed, Aug 12, 2009 at 2:44 PM, Marvin Froeder <[email protected]> wrote:
> Well,
> That won't work due to maven limitations.... you need to declare the
> dependencies present on flex-framework one by one with the external scope.
>
>
> VELO
>
>
> On Wed, Aug 12, 2009 at 9:33 AM, Marc Speck <[email protected]> wrote:
>
>> you mean:
>>
>> <dependency>
>> <groupId>com.adobe.flex.framework</groupId>
>> <artifactId>flex-framework</artifactId>
>> <version>4.0.0.8811</version>
>> <scope>external</scope>
>> <type>pom</type>
>> </dependency>
>>
>>
>>
>>
>>
>>
>> On Wed, Aug 12, 2009 at 2:29 PM, Marvin Froeder <[email protected]>wrote:
>>
>>> Ow, then set the scopes to external and be happy =D
>>>
>>> VELO
>>>
>>>
>>> On Wed, Aug 12, 2009 at 9:28 AM, Marc Speck <[email protected]> wrote:
>>>
>>>> exactly,
>>>> Marc
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Aug 12, 2009 at 2:25 PM, Marvin Froeder <[email protected]>wrote:
>>>>
>>>>> You have one pom per module?
>>>>> VELO
>>>>>
>>>>>
>>>>> On Wed, Aug 12, 2009 at 9:20 AM, Marc Speck <[email protected]>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 12, 2009 at 2:12 PM, Marvin Froeder <[email protected]>wrote:
>>>>>>
>>>>>>> But if you are not using modulesFiles, how do you expect flexmojos to
>>>>>>> know if your app is a module or not?
>>>>>>
>>>>>>
>>>>>> Well, that's the reason I asked.
>>>>>> Each module is in a separate project and the Class that extends Module
>>>>>> is always in the root. So I guessed that the compiler recognizes the
>>>>>> extended Module class. The compiled modules work fine with ModuleManager.
>>>>>>
>>>>>> Marc
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> VELO
>>>>>>>
>>>>>>> On Wed, Aug 12, 2009 at 9:06 AM, Marc Speck <[email protected]>wrote:
>>>>>>>
>>>>>>>> https://issues.sonatype.org/browse/FLEXMOJOS-172
>>>>>>>>
>>>>>>>> Marc
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Aug 12, 2009 at 1:51 PM, Marvin Froeder
>>>>>>>> <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> Sure, create a subtask here:
>>>>>>>>> https://issues.sonatype.org/browse/FLEXMOJOS-39
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <https://issues.sonatype.org/browse/FLEXMOJOS-39>VELO
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Aug 12, 2009 at 8:49 AM, Marc Speck
>>>>>>>>> <[email protected]>wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Aug 12, 2009 at 1:44 PM, Marvin Froeder <velo.br@
>>>>>>>>>> gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Aug 12, 2009 at 8:21 AM, Marc Speck <[email protected]
>>>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> 1. I run into moduleFiles and I'm not really sure what it is
>>>>>>>>>>>> for: "The list of modules files to be compiled." Modules seem to
>>>>>>>>>>>> compile
>>>>>>>>>>>> fine without this parameter.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> This is for flex mx:Modules.... flexbuilder like, messing all
>>>>>>>>>>> sources into same tree...
>>>>>>>>>>>
>>>>>>>>>> ah, it's for the case when you mix the application and modules in
>>>>>>>>>> the same project. Ok, don't need that.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2. I bumped into the problem described in "Building an
>>>>>>>>>>>> Application with RSLs causes Modules to be built with RSLs",
>>>>>>>>>>>> http://bugs.adobe.com/jira/browse/FB-15470 in Flex Builder 3
>>>>>>>>>>>> with Flex 4. Is there a parameter in flex-mojo for this? It
>>>>>>>>>>>> basically
>>>>>>>>>>>> shuffles all SDK libs from runtime-shared-libraries to
>>>>>>>>>>>> external-library-path
>>>>>>>>>>>> for modules. Obviously, there's no need for the feature as long as
>>>>>>>>>>>> Flex 4 is
>>>>>>>>>>>> not released but it might help if you were not aware (or I don't
>>>>>>>>>>>> understand
>>>>>>>>>>>> here something :)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Flexmojos doesn't handle that, but it can be included....
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Well, there is time until Q1 2010... Shall I create an issue?
>>>>>>>>>>
>>>>>>>>>> Marc
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> VELO
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en
http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---
