Externalizing sfapi.swc

[Adam Cheney]

Hi Folks,

We're considering using this library for automated testing of our flex applications using Selenium - the problem is that we have a complex and lengthy approval process that I'm seeking to avoid. The thing is, it would not apply to this library if it does not make it as far as production - so, does the swc *have* to be built in to the swf, or is there any way it be externalized somehow?

Cheers - Adam...

[Fergal Hanley]

Yes the swc, as it is right now, has to be included at compile time. Building the swc into the app is simply a matter of including a command line argument when compiling. You could have a separate set of arguments configured for your test environment build process to include the swc, and another set that doesn't include it in the production build.

--

---
You received this message because you are subscribed to the Google Groups "Selenium-Flex API - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sfapi-suppor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Adam Cheney]

Hi Fergal,

Thanks for the info.

I'm fine with the technicalities of including it in a build (we use an Ant/Ivy/Nexus build) but the problem is that our central build server farm (controlled outside my team) uses a tool to identify unapproved dependencies at build time. Even the "non-Prod" build would have to go through this process, so the library will need to be approved for us to use it, even though it is not going anywhere our production environment.

Thanks for the info. I'll have a think about other strategies - unfortunately, the approval process is a bit like running a marathon thorough treacle...

Adam.