Hello VELO,

No, my guess is that flex-mojos is not to blame.

The associated default flex-mojos compiler option behavior is definetely
different from the FlashBuilder default compiling options, But it's not the
first time, and won't be the last.

Cheers,
François


On Mon, Sep 27, 2010 at 3:51 PM, Marvin Froeder <[email protected]> wrote:

> Just to be sure, it isn't flexmojos related then, right?
>
> 2010/9/27 François Le Droff <[email protected]>
>
>> FYI,
>> I just found the missing parameter :
>>
>> <useResourceBundleMetadata>false</useResourceBundleMetadata>
>>
>> Cheers,
>> François
>>
>>
>> 2010/9/27 François Le Droff <[email protected]>
>>
>> Hello guys,
>>>
>>> I'm facing the issue that was discussed in the thread below:
>>> My i18ned libraries when built with flex-mojos (3.7) include all the sdk
>>> resource-bundles in their catalog.xml.
>>> This proves to be an issue for later use in I18N applications.
>>> Is there a bug for this one in Jira ?
>>> Does any one has a workaround ?
>>>
>>> Cheers,
>>> François
>>>
>>>
>>>
>>> On Tue, Apr 28, 2009 at 2:35 AM, dtornkaew <[email protected]> wrote:
>>>
>>>>
>>>> My SWC doesn't have any of the Flex *.properties files in the /locale/
>>>> en_US directory. However if I look at the catalog.xml it does have the
>>>> following.
>>>>
>>>> <script name="en_US$core_properties" mod="1234166223521" >
>>>>        <def id="en_US$core_properties" />
>>>>        <dep id="AS3" type="n" />
>>>>        <dep id="mx.resources:ResourceBundle" type="i" />
>>>> </script>
>>>> <script name="en_US$logging_properties" mod="1231356741852" >
>>>>        <def id="en_US$logging_properties" />
>>>>        <dep id="AS3" type="n" />
>>>>        <dep id="mx.resources:ResourceBundle" type="i" />
>>>> </script>
>>>> <script name="en_US$containers_properties" mod="1234166223505" >
>>>>        <def id="en_US$containers_properties" />
>>>>        <dep id="AS3" type="n" />
>>>>        <dep id="mx.resources:ResourceBundle" type="i" />
>>>> </script>
>>>> <script name="en_US$collections_properties" mod="1234166223505" >
>>>>       <def id="en_US$collections_properties" />
>>>>       <dep id="AS3" type="n" />
>>>>       <dep id="mx.resources:ResourceBundle" type="i" />
>>>> </script>
>>>>
>>>> I didn't paste all of them here but it looks to me like all transient
>>>> dependencies that have resource bundles in them are getting compiled
>>>> in even though they are marked scope "external".
>>>>
>>>> Lance
>>>>
>>>> On Apr 27, 7:18 pm, Marvin Froeder <[email protected]> wrote:
>>>> > Check your SWC.  It probably contains flex SDK resource bundles.....
>>>> so it
>>>> > got duplicated and FDK doesn't compile.
>>>> > VELO
>>>> >
>>>> > On Mon, Apr 27, 2009 at 9:09 PM, dtornkaew <[email protected]> wrote:
>>>> >
>>>> > > That was my initial thought too but I double checked all
>>>> dependencies
>>>> > > that I am compiling (using mvn dependency:tree) and they are all on
>>>> > > the same version of Flex. One exception is PureMVC but it is also
>>>> > > marked as scope "external" on all libraries.
>>>> >
>>>> > > Something I noticed is when I turn on "keep-generated-code" Flex
>>>> > > Compiler is creating classes for all resource bundles that are
>>>> > > resolved even bundles that are marked "external". My fear is that
>>>> > > these are getting compiled in to all of my libraries and conflicting
>>>> > > with each other when they are later used with "include-libraries"
>>>> > > which is the case with the unit tests.
>>>> >
>>>> > > As soon as I get time I will build out some small scale projects and
>>>> > > do further testing.
>>>> >
>>>> > > Thanks for the help and suggestions!
>>>> > > Lance
>>>> >
>>>> > > On Apr 27, 3:26 pm, Marvin Froeder <[email protected]> wrote:
>>>> > > > This seem to be a problem on your libraries... like something
>>>> built with
>>>> > > > flex 3.2 mixed with something built using 3.3
>>>> >
>>>> > > > VELO
>>>> >
>>>> > > > On Mon, Apr 27, 2009 at 5:11 PM, dtornkaew <[email protected]>
>>>> wrote:
>>>> >
>>>> > > > > VELO,
>>>> >
>>>> > > > > I Put "compile" and "merge" on the library-path and "internal",
>>>> > > > > "external", "test", "rsl", "caching", "getDefaultLocale()",
>>>> > > > > "runtimeLocales" and "compiledLocales" all on the
>>>> include-libraries
>>>> > > > > and I get the same problem.
>>>> >
>>>> > > > > I get the following error on rpc.rb.swc and
>>>> datavisualization.rb.swc:
>>>> > > > > [ERROR] /home/llinder/.m2/repository/com/adobe/flex/framework/
>>>> > > > >
>>>> datavisualization/3.3.0.4852/datavisualization-3.3.0.4852-en_US.rb.swc
>>>> > > > > $locale/en_US/skins.properties:[16,34] Incompatible override.
>>>> > > > > override protected function getContent():Object
>>>> >
>>>> > > > > I also get this error for each of the standard flex resource
>>>> bundles:
>>>> > > > > [ERROR]
>>>> /home/llinder/gjobs/md/data_tracking/trunk/datatracking-flex-
>>>> > > > > project/datatracking-flex-framework/target/datatracking-flex-
>>>> > > > >
>>>> framework-1.0.1.0-SNAPSHOT.swc(en_US$collections_properties):[-1,-1]
>>>> > > > > Incompatible override.
>>>> >
>>>> > > > > This seems like a bug with Flex Builder but I can't nail down
>>>> > > > > specifically what is causing it.
>>>> >
>>>> > > > > For now I am going back to "internal", "test", "rsl", "caching"
>>>> on the
>>>> > > > > include-libraries and everything else on library-path :-(
>>>> >
>>>> > > > > When time permits I will put together a set of sample projects
>>>> to
>>>> > > > > duplicate the issue. In the main time if you or anyone else has
>>>> any
>>>> > > > > more thoughts I will gladly try them out!
>>>> >
>>>> > > > > Thanks!
>>>> > > > > Lance
>>>> >
>>>> > > > > On Apr 27, 1:04 pm, Marvin Froeder <[email protected]> wrote:
>>>> > > > > > Wow, this is a serious issue on flex compiler....
>>>> > > > > > I think is possible to workaround it by changing the test to
>>>> include
>>>> > > all
>>>> > > > > > locales available.... but not sure if that is a wise decision.
>>>> > > > > > I mean, does some see any problem on including all resource
>>>> bundles
>>>> > > > > > available into the test SWF?
>>>> >
>>>> > > > > > VELO
>>>> >
>>>> > > > > > On Mon, Apr 27, 2009 at 1:49 PM, Dtornkaew <[email protected]
>>>> >
>>>> > > wrote:
>>>> >
>>>> > > > > > > When compiling multiple SWC libraries AND marking all
>>>> dependencies
>>>> > > as
>>>> > > > > > > scope "external" the unit tests won't compile. The Flex
>>>> Compiler
>>>> > > error
>>>> > > > > > > complains about incompatible overrides on the generated
>>>> locale
>>>> > > > > > > classes.
>>>> >
>>>> > > > > > > This problem arises when I create 2 SWC libraries where
>>>> library B
>>>> > > > > > > depends on library A and both library A and B have locales
>>>> and I
>>>> > > mark
>>>> > > > > > > both libraries with compileLocales property and all
>>>> dependencies on
>>>> > > > > > > library A and B are marked to scope "external".
>>>> >
>>>> > > > > > > I have been able to fix the problem by changing
>>>> TestCompilerMojo to
>>>> > > > > > > put all "external" and "test" dependencies on the
>>>> library-path
>>>> > > instead
>>>> > > > > > > of on the include-path. When I do this everything works
>>>> fine.
>>>> >
>>>> > > > > > > I am torn... I know there are problems with the Automation
>>>> > > framework
>>>> > > > > > > and Unit Tests if all dependencies marked "test" are not on
>>>> the
>>>> > > > > > > "include-path" but at the same time there are problems with
>>>> > > compiling
>>>> > > > > > > multiple dependent SWCs with compiled locales. The only way
>>>> I can
>>>> > > see
>>>> > > > > > > to solve this problem is for more scopes such as
>>>> "test-internal"
>>>> > > and
>>>> > > > > > > "test-merged" but this is not my decision to make... just my
>>>> > > > > > > problem :'(
>>>> >
>>>> > > > > > > Anyone have suggestions or run into this problem before?
>>>> >
>>>> > > > > > > The reason I am using scope "external" for all dependencies
>>>> on my
>>>> > > > > > > libraries is to attempt to keep my libraries free of
>>>> transient
>>>> > > code.
>>>> >
>>>> > > > > > > Thanks,
>>>> > > > > > > Lance
>>>> --~--~---------~--~----~------------~-------~--~----~
>>>> 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]<flex-mojos%[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/
>>>> -~----------~----~----~----~------~----~------~--~---
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> François Le Droff
>>> http://www.droff.com
>>>
>>>
>>
>>
>> --
>>
>> François Le Droff
>> http://www.droff.com
>>
>>  --
>> 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]<flex-mojos%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/flex-mojos
>>
>> http://flexmojos.sonatype.org/
>>
>
>  --
> 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]<flex-mojos%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>
> http://flexmojos.sonatype.org/
>



-- 

François Le Droff
http://www.droff.com

-- 
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

http://flexmojos.sonatype.org/

Reply via email to