Flex-mojos: Maven 2 plugins for Flex

A bug was found on modules support.

So its force me to release a beta 3.

So, its out.

Good modules for every one.

VELO

Hi people,

Busy week.

Some issue, and, tadaaam…. new version.

AsDoc got an important update, now it is a maven report. Thanks Justin.

This guy found some bugs on flexunit support. Issues 13, 14 and 15.

All fixed.

This week I look at a interesting discussion on Israfil list (well, I was user some time ago, and I don’t leave the list).

This let me to create the issue 11. There is now a new way to use modules.

Is possible generate multiple artifacts (One application and several modules) from only one source folder. Personally I don’t like this. I will not use. But is how Adobe first presents module support. So, who wanna use modules link FlexBuilder support can do on flex-mojos.

See sample here.

So, good weekend for all. I will get some time on beach.

VELO

To finish the series, Sebastien publish the two final parts (I miss part 3 to publish =)

So there is:
Flex, Spring and BlazeDS: the full stack! (Part 3)
Flex, Spring and BlazeDS: the full stack! (Part 4)

So, I recommend a look at final parts.

Good codes.

VELO

Time to time I hear something about flex swf files size.

Seems Adobe hear that too.  So, on Flex 3 Adobe starts a new initiative to resolve that, Framework Caching.

And how to use it on flex-mojos?

I quite complicated, but I will try to explain that.

To use as base I recommend this very complex hello world application.

The project structure like this:

Now, lets edit pom.xml.

First add the caching scope dependency:

<dependencies>
  <dependency>
    <groupId>com.adobe.flex.sdk</groupId>
    <artifactId>framework</artifactId>
    <version>3.0.0.3.0.0.477</version>
    <type>swc</type>
    <scope>caching</scope>
  </dependency>
</dependencies>


This define to use flex framework on caching. But where the flash player must look for this files?
In order to define the RSLs location we need to do a second change on pom.xml:

<build>
  <plugins>
    <plugin>
      <groupId>info.rvin.mojo</groupId>
      <artifactId>flex-compiler-mojo</artifactId>
      <configuration>
        <rslUrls>
          <rsl>{artifactId}-{version}.{extension}</rsl>
        </rslUrls>
      </configuration>
    </plugin>
  </plugins>
</build>


On rslUrls are defined the paths to look for RSLs.

Run mvn install and copy simple-flex-library-1.0-SNAPSHOT.swf and framework-3.0.0.3.0.0.477.swz to same directory on some web server to run.

Quite simple, isn’t it?
If you don’t wanna edit the pom, just download it from here.

Good caching for every one.

VELO

To start weekend I promove flex-mojos compiler to beta1.

This beta add a better support for RSL and add a simplier support for Flex Caching Framework (Will write about this soon).

This relase add some minor fix on asdoc.

Two new mojos.  For flex-builder and for sources.  Flex-mojos source plugin is based on Java source plugin.  So its begin very stable.

Flex builder mojos isn’t usable for now.  Is on a pre-alpha stage.  The main goal is made a plugin who mimics eclipse plugin.  Help acceptable =D

Waiting for feedback.

VELO

Today Sébastien publish the second part of his tutorial.
http://sebastien-arbogast.com/index.php/2008/04/11/flex-spring-and-blazeds-the-full-stack-part-2/

I recommend the visit.

VELO

We got a new house.

Now we are on a private server (provided by Joost den Boer).

Here we have more space for flex mojos documentation and some other plans.

Welcome all, wait for news and stay tun.

VELO

Today Sébastien post the first part about Flex, Spring and BlazeDS tutorial.

That is good. But what is the relation whit flex-mojos?
He is using flex-mojos on the tutorial =D

So I recommend a look here.

VELO

Welcome to the flex-mojos website.

We’re currently in the process of setting up this site and hope to have more information here soon.
For now more information can be found on:

• The flex-mojos blog
• Our google code site
• Our discussion group
• Our maven repository

Since alpha4 flex-mojos has support to asdoc generation.

Is quite easy to get it working.

Who is using the suggested super pom, just need go to console and type:

mvn asdoc:asdoc

That is why I create and insist on the use of super pom. Even for Java maven has a super pom. So I do the same thinking in Flex.

For those who can’t or just don’t wanna use flex-mojos super pom is easy to put asdoc to run. Just add a plugin on pom.xml:

<build>
...
  <plugins>
  ...
    <plugin>
      <groupId>info.rvin.mojo</groupId>
      <artifactId>asdoc</artifactId>
    </plugin>
  </plugins>
</build>

Once is dont, just maven on the same way of who uses super pom.

For who doesn’t wanna, can, like… change pom.xml, there is always a harder way. Type:

mvn info.rvin.mojo:asdoc:1.0-alpha1:asdoc

1.0-alpha1 is the current version of asdoc-mojo.
Check for most updated versions.

With asdoc on first alpha, a lot of problems may be found. On basic tests is working, if someone find problems let me know.

VELO