Yes, as I mentioned above (first item in "steps so far" section).

BTW: FlexMojos 4 ignores the -DflashPlayer.command switch entirely.  I 
installed a debug flash player in my local .m2 repo as a workaround.

On Thursday, September 8, 2011 9:58:06 AM UTC-7, velo wrote:
>
> Did you tried debugger player as people already suggested?
>
> VELO
>
> On Thu, Sep 8, 2011 at 1:49 PM, pmbauer <[email protected]> wrote:
>
>> That doesn't help since I need to read *FlexMojos* trace statements 
>> generated from a run kicked off from maven - no browser, and no way to 
>> attach a debug process to the player that pops up for all of 1 second for 
>> the unit tests.
>> Velo, how do you see the trace statements when you are debugging 
>> FlexMojos?
>>
>> On Thursday, September 8, 2011 4:56:52 AM UTC-7, Alexandre Reis wrote:
>>>
>>> You need to connect the flex debugger to your application in order to see 
>>> the trace statements. You application also needs to be compiled with the 
>>> <debug>true</debug> option in flex-mojo's configuration.
>>>
>>> If you're using firefox with firebug, you can skip the debugger using 
>>> http://code.google.com/**p/flash-thunderbolt/wiki/**ThunderBoltAS3<http://code.google.com/p/flash-thunderbolt/wiki/ThunderBoltAS3>
>>>
>>> Regards,
>>>
>>> Alexandre M. Reis
>>>
>>>
>>>
>>> On Wed, Sep 7, 2011 at 9:50 PM, pmbauer <[email protected]> wrote:
>>>
>>>> *Scenario:*
>>>> FlexMojos liberally uses trace(...) statements all over its code base.
>>>> I have a custom build of FlexMojos that I am attempting to debug.
>>>>
>>>> *Problem:*
>>>> I cannot find where the trace(...) statements are being written to.
>>>> The statements are not anywhere in the mvn output, files in the target 
>>>> folder, or in my TraceOutputfileName (~/mm.cfg)
>>>>
>>>> *Steps so far:*
>>>> I'm using a debug flash player.
>>>> I've added the -Dflex.omitTraceStatements=**false to my FlexMojos build
>>>> I've added the -Dflex.omitTraceStatements=**false to my test project
>>>> My ~/mm.cfg file has a key TraceOutputfileName that points to a trace 
>>>> log file
>>>>
>>>> Any ideas? I'd rather not have to replace all the trace statements in 
>>>> FlexMojos with other logging facilities.
>>>>
>>>> -- 
>>>> 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
>>>> flex-mojos+...@googlegroups.**com
>>>> For more options, visit this group at
>>>> http://groups.google.com/**group/flex-mojos<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]
>> 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]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to