Max Did It
Tagged ,

Committing Artifacts with Ivy

In my last post, I talked about the build automatisation tool Apache Ant. Ant originated as a tool for Java developers and has been succeeded by Maven, which provides many nice features like dependency management.

Imagine you wouldn't have to download and copy any libraries into your project path and configure the classpath every time you start a new project or a new version of a library comes out. What if you had a tool that did that automatically for you? Maven does that, and more.

The Trouble With Flash And Maven

I guess for a Java developer there is currently no good reason to use Ant instead of Maven, but if you work with Actionscript or Flex, things are a little more complicated. Right now, FlexMojos is the only current plugin for Maven that allows you to compile SWF or SWC files.

Now, when FlexMojos happens to do what you want it to do, it's great! It's convenient and you can set up projects with unit tests and code coverage very quickly. However, if FlexMojos doesn't do what you expect it to, and that still happens quite often, you will have a very hard time figuring out what the problem is and how to fix it.

Because of this, I decided to keep using Ant to build my Actionscript projects for the moment. However, you can use Maven's automatic dependency management feature in Ant build scripts as well.