New SVN repository

First the blog was moved.

Now, SVN is under a new domain:
http://svn.sonatype.org/flexmojos

The flex-mojos is going to Sonatype forge. This is just the first step.

Stay tunned.

VELO

10 Responses to “New SVN repository”

  1. Are you moving out of google code, and why?

  2. The flex-mojos is going to Sonatype forge. SVN is just the first step.

    VELO

  3. Yes, but why?

  4. Well, Jason (maven creator) invite me. And I like the idea.

    Sonatype is a cool company specially when you have maven in mind.

    Why are you curios?

    VELO

  5. Okay.

    I am thinking about doing support for the use of fcsh in one of the current maven flex plugins: Yours or israfil. This is why I came around to the sources/svn and saw they were moving. I was curious, because it seems like google-code has much more to offer, with respect to online tools like the wiki, issue management etc.

    Would you be interested in me working on support for the use of fcsh in your flex-compiler mojo?

  6. Under israfil makes much sense use FCSH, because call mxmlc/compc over and over again doesn’t have a performance.

    Flex-mojos uses flex-compiler-oem. So I just call compiler API, like what flexbuilder does. So, once flex-compiler-oem is into memory it begin to works like FCSH.

    But each time you type mvn install you will need to reload flex-oem-compiler. Using FCSH it can still on memory.

    But is possible to do something like this:
    http://stopcoding.wordpress.com/2008/05/16/the-flex-compiler-api-rpc-style/

    That will be cool. Very cool =P

    Then flex-mojos can run on 3 levels. Standard (current), local (just run RPC on same local machine) and server (run RPC on a remote machine, that will require transfer files over network).

    Sounds cool to you?

    Wanna do that?

    VELO

  7. I think fcsh makes sense in both israfil and in flex-mojos. If I have only one module to compile with flex code in flex-mojos, I still have to pay the compiler bootstrap/loading proces each time I execute mvn.

    What I was thinking about was what you describe as “local”, that is, rpc of some sorts from flex-mojos but to a local running fcsh process. But, maybe it would be better to do a flex oem compiler server, instead of using fcsh. The goal is the same though.

  8. Do what you wanna do makes sense.

    Just not using FCSH. FCSH make sense on israfil. O Flex-mojos makes more sense use flex-compiler-oem. But I think you figureout this already.

    I add you at gtalk. Lets talk about this.

    VELO

  9. Can you post something about the move on the google site?

  10. Done, just a small alert…
    On SVN too.

    VELO

Discussion Area - Leave a Comment