I've pushed my changes to my fork on github at
http://github.com/rlogiacco/flexmojos/tree/flexmojos-3.x, I like your
review and suggestions before requesting a pull, it is my very first
contribution to flexmojos.



On Jan 17, 5:18 pm, rlogiacco <[email protected]> wrote:
> Hi all,
> I've produced an update for flexmojos-3 to fix the problem regarding
> metadata and the optimize goal, I'll push the changes on my branch on
> github and I'll request a pull and a release, but I'm still
> experiencing problems with parlsey metadata (which is the reason I
> started working on flexmojos)http://tinyurl.com/4nkmvm6
>
> Before going further, I've red almost everything I was able to find on
> the topic which seem resolved into flexmojos-4 but we want to continue
> to use flexmojos-3 for the moment so flexmojos-4 is not an option.
>
> I understood the problem in the link is due to a missing option
> providen to the optimization process, specifically it is about the -
> keep-as3-metadata which (I'm guessing here) instruct the optimizer to
> avoid to strip out some metadata information (those specified) from my
> script files while performing optimization.
>
> I slightly changed the OptimizerMojo class to provide that list to the
> optimization process, but it seems it just ignores that parameter. The
> only way I was able to use flexmojos-3 to produce RSLs is avoiding the
> optimization process at all (I've developed a different MOJO that gets
> the library.swf from the SWC without performing the optimization and
> digest steps.
>
> My question is: is this a known bug of the API.optimize ( ... )
> method? Can someone have a look to my changes to check if I made some
> mistake in using the adobe API? (http://pastebin.com/zHEvVM2N)
>
> I've added an additional MOJO which will help in retrieving RSLs from
> the repositories eventually running the optimization process in case
> the SWF file is not yet available, something already available on
> flexmojos-4 which can be useful for our project and I wished to share.
>
> As my firewall prevents me to push to github I'll put this stuff on my
> fork as soon as possible and I'll request a pull and, possibly, a
> release.
>
> Thanks,
>   Roberto

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