Thanks for the quick answers guys!

Finally got it working :)

Sriraman, I used mvn install-install file instead of
flex.mojos:install-sdk and it worked too.
Thanks anyway for your contribution, it helped me realize that I was
using the wrong files to install the resource bundle automation swc in
my repository.

@VELO : Indeed, I was also doing wrong on this part , thanks for the
clarification

On 5 juin, 07:41, Sriram Gopalan <[email protected]> wrote:
> Hi,
>
> We had a nightmare getting the automation libraries into Flex 3.3.0.4852
> build. Finally, we figured out the steps as detailed below:
>
> 1. Flex 3.3.0.4852 SDK does not come with automation libraries. They can be
> found in the 3.0.0 SDK under the framework/libs folder. The
>     following are the library files:
>     a) automation.swc
>     b) automation_agent.swc + 2 more actually automation_dmv.swc and
> automation_flashflexkit.swc. But you will require only the first two.
>
> 2. Copy these two files to the 3.3.0.4852 SDK's framework/lib folder.
>
> 3. The other 2 files relate to the resource bundles for the above two
> framework components viz
>     a) automation_rb.swc
>     b) automation_agent_rb.swc
>
> 4. Copy the above two files to the flex 3.3.0.4852 SDK's
> frameworks/locale/en_US
>
> 5. Use the flex-mojos.install-sdk mojo to deploy the flex sdk artifacts into
> your local maven repository.
>
> 6. Follow the links as suggested by Logan and you should get things working.
>
> The actual problem starts only when you want localization for your
> application. Typically you would use the copylocale utility to
> get the resource bundles for your framework components. However, the
> resource bundles for the automation libraries are not copied.
> Possibly a bug? I don't know. However, there is a workaround for this also.
> We created a maven project with a dummy mxml file
> referring to the bundles in the automation libraries and used the flex-mojos
> to create the resource bundles for the target locale.
>
> best regards
> sriraman.
>
> On Fri, Jun 5, 2009 at 6:16 AM, PeZ <[email protected]> wrote:
>
> > Ok, I'm stuck once more :-/
>
> > So I added theses dependencies :
>
> > <dependency>
> >                <groupId>com.adobe.flex.framework</groupId>
> >                <artifactId>automation</artifactId>
> >                <version>3.2.0.3958</version>
> >                <type>swc</type>
> >               <scope>test</scope>
> >        </dependency>
>
> > <dependency>
> >                <groupId>com.adobe.flex.framework</groupId>
> >                <artifactId>automation_agent</artifactId>
> >                <version>3.2.0.3958</version>
> >                <type>swc</type>
> >               <scope>test</scope>
> >        </dependency>
>
> > But it lead to 2 other errors :
>
> > [ERROR] Unable to resolve resource bundle "automation_agent" for
> > locale "en_US".
> > [ERROR] Unable to resolve resource bundle "automation" for locale
> > "en_US".
>
> > So I changed my config to :
>
> >       <dependency>
> >                <groupId>com.adobe.flex.framework</groupId>
> >                <artifactId>automation</artifactId>
> >                <version>3.2.0.3958</version>
> >                <type>rb.swc</type>
> >                <scope>test</scope>
> >                <classifier>en_US</classifier>
> >        </dependency>
>
> >        <dependency>
> >                <groupId>com.adobe.flex.framework</groupId>
> >                <artifactId>automation_agent</artifactId>
> >                <version>3.2.0.3958</version>
> >                <type>rb.swc</type>
> >                <scope>test</scope>
> >                <classifier>en_US</classifier>
> >        </dependency>
>
> > Unfortunately , I still have a message telling me Automation manager
> > is missing. Any idea?
>
> > On 4 juin, 20:15, PeZ <[email protected]> wrote:
> > > well nevermind, there was a hidden Alert message about automation
> > > manager missing ... forgot to set the scope to test.
>
> > > I'll work on it tonight again and see if it works :)
>
> > > On Jun 4, 7:53 pm, PeZ <[email protected]> wrote:
>
> > > > Thanks Logan.
>
> > > > I have a question for you then : Do I need to use a template MXML like
> > > > the example posted on the blog or should I test against my main MXML?
> > > > I've tried both actually but tests fail, I always get an "Error #1009:
> > > > Cannot access a property or method of a null object "
> > > > (Tests are ok when I launched them manually.)
>
> > > > On Jun 4, 6:29 pm, Logan Allred <[email protected]> wrote:
>
> > > > > On Thu, Jun 4, 2009 at 7:51 AM, PeZ<[email protected]> wrote:
> > > > > > I'd like to integrate my FlexMonkey UI tests in Flex mojos. The
> > > > > > problem is I haven't found any documentation/how-to that work with
> > the
> > > > > > lastest FlexMonkey (8.0) & FlexMojo releases (3.2.0).
>
> > > > > > I don't need a step by step tutorial but just some guidelines
> > because
>
> > > > > We just got FlexMonkey 0.8a running in our build. I mostly followed
> > > > > the instructions here:
>
> > > > >http://flex-mojos.info/2008/11/20/the-return-of-automated-ui-tests/
>
> > > > > We already have FlexUnit tests running in our build, and as I recall,
> > > > > it went pretty smooth.
>
> > > > > I think we added FlexUnitTests.as and MonkeyContacts.mxml to
> > > > > src/test/flex and FlexMonkeyEnv.xml to src/test/resources, put the
> > > > > appropriate automation libs in the pom (we already had a working
> > > > > automation build, but we did have to tweak it a bit) and it pretty
> > > > > much just worked.
>
> > > > > Give it a try and see what happens, let us know if you have problems.
>
> > > > > Logan
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---

Reply via email to