Thursday, March 4, 2010

Hardly a Flex-ible Journey: Moving from Flex 4-Beta 2 to a Stable Build Or Nightly Build

  1. Search and replace all instances of with the desired version ( in my case) which hopefully has already been published to maven or you have uploaded to your local repository.
    1. com.adobe.flex:flex-framework and com.adobe.flex.framework:compiler were updated for me
  2. Change the version of your org.sonatype.flexmojos:flexmojos-maven-plugin to be 3.6-SNAPSHOT
    1. Usually the repository for this is the following one:
    2. Make DAMN sure that in your repository definition you have the snapshots enabled set to true
  3. Some of the locale related SWC files are not published on the maven repositories but you can overcome that by downloading the SDK and uploading the missing files manually to your local maven repository.
  4. Don't forget to tell your Flash Builder IDE about the SDK ... Project > Properties > Flex Compiler > Use a specific SDK: Flex 4.0 (build 13875)
  5. Replace all instances of xmlns:mx="library://" with xmlns:ns="library://" using your favorite tool, mine is pspad.
  6. Replace all instances of mx: with ns:
  7. Follow the instructions from this post to get your code compiling. Note: I said compiling ... not functioning!
  8. Update your injection libraries if you use any. I use Parsley so I went and downloaded parsley-2.2.0 and YES if you use maven then you also need to update the parsley version in pom.xml in order to use it.

Wednesday, March 3, 2010

Sun "internal" packages: Maven vs Eclipse

When working with any java classes that have the word "internal" in their package name you'll notice that your build will compile just fine in Eclipse but fail when compiled via Maven.

If you want an intelligent guess at why this may be happening, you can refer to this useful post which talks about this issue in more detail.