Le 29 oct. 08 à 17:06, Michael Schmalle a écrit : > Hi, > > I can say ANT is your answer, build the SWC using it. I have very > complex libraries, and all I maintain is a simple ant xml included > file (that is imported from the master build file, this includes > multiple project library builds at once) that lists the front end > class clients, the linker resolves the rest. > > This way you can checkout and commit these files in collaboration. > > Mike
Hi ! I was exactly waiting for an answer like that. I'm desperatly trying to build a system which would do exactly what Flex Builder does except better ;^) Our projects include * Third-Party libs (like google modified google code flex lib), * In-house libs (AS3 and/or MXML components), * Our Flex app project + all the server-side code (java), * In-house html template and so on. Then we export release build and build war to deploy on our Tomcat Server I'm dreaming of automating the process and checking out and run tests automatically. Doy you happen to have an example of your ant file ? I think what you describe is close to what I want to achieve. It would be very kind , Thanks in advance, Farid from Paris, France
