Compile Fails When Attepmting to Link Flexmonkey into Existing App
Closed this issue · 3 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Add the FlexMonkey.swc to the libs of an existing flex project as
described in the documentation.
2. Add the additional command line arguments needed to link flexmonkey into
the existing app as described here:
http://code.google.com/p/flexmonkey/wiki/LinkingFlexMonkeyIntoApp
3. Press OK to confirm the changes and recompile the project.
What is the expected output? What do you see instead?
The compile will fail with with the error "Unable to locate resource bundle
automation.swc for local en_US". This error is also thrown for a number of
other swc files that cannot be located.
I tried copying the contents of the /libs folder into the /locales/en_US
folder and still get the same errors.
What version of the product are you using? On what operating system?
FlexMonkey 0.8a, Windows XP SP3, flexbuilder sdk 3.2
Original issue reported on code.google.com by bucpa...@gmail.com on 21 May 2009 at 4:06
GoogleCodeExporter commented
Turns out it was a problem with flexbuilder, not flexmonkey. The automation
swcs were
in the correct directories, but the automation_rp swcs were missing. If anyone
else
runs into this just copy the missing files from an older version of the flex 3
sdk (I
used 3.1)
Original comment by bucpa...@gmail.com on 22 May 2009 at 2:51
GoogleCodeExporter commented
Note that the "automation_rp" swcs are actually "automation_rb", and are
located at
sdks/[version]/frameworks/locale/[locale]/. More info here:
http://www.modelmetrics.com/general/setting-up-automated-testing-in-flex-sdk-330
/
Original comment by googlegr...@gersic.com on 26 Jun 2009 at 4:37
GoogleCodeExporter commented
Retiring 0.x issues
Original comment by eric.owe...@gtempaccount.com on 16 Jul 2009 at 12:51
- Changed state: WontFix