Renaun,
We use ANT on developer machines and on the server for deployment. Typically a
single build.xml file sits in the root of the SVN repository for a project. We
typically define tasks for incremental SWF and RSL compilation, java
compilation, and larger tasks for ground up builds. The
hi ted,have you got an example of a flex2 mxmlc ant script that works properly?ThanksjohanOn 3/23/06, Ted Patrick
[EMAIL PROTECTED] wrote:Renaun,We use ANT on developer machines and on the server for deployment. Typically a single
build.xml file sits in the root of the SVN repository for a
The real key to ANT is leveraging the depends property.
target name=flex.build depends=rsl.build /
In this case calling ANT flex.build, will first run rsl.build just before
running flex.build. depends allows you to create a very large build from very
small encapsulated
_
From:
The real key to ANT is leveraging the depends property.
target name=flex.build depends=rsl.build /
In this case calling ANT flex.build, will first run rsl.build just before
running flex.build. depends allows you to create a very large build from very
small encapsulated tasks. It is the lever
thats the fastest for sure. personally i use mxmlc directly,but it gets
a wee bit slow when the project gets big. one of my team members tried
the fastmxmlc but according to him there weren't any/very little
increase in compile timesOn 3/22/06, Renaun Erickson [EMAIL PROTECTED] wrote:
After
hear hear on what david says. using ant we
update from svn
build unit tests app using mxmlc, if all tests pass
use mxmlc to build app
so yeah it has its benefits :)
so it is critical to the process asOn 3/22/06, Dave Wolf [EMAIL PROTECTED] wrote:
That depends what you mean by better.In Flex
this is both for develpers (developer chooses which target to compile -
unitests,app or all) and our continues integration server. we only
deploy a swf to production.On 3/22/06, Renaun Erickson [EMAIL PROTECTED] wrote:
Thanks Johannes for insight.Is this what you do as a developer on a dev
My question then would be, is the speed of compilation a main factor
in the choice of compilation methods?
well as i orignally stated the appserver approach is the fastest, so if
its speed you are after, yeah go for it. some of the larger projects i
have worked on has taken up to a 1:30 but
i have not been able to get mxmlc working like i want to in flex2 using
ant yet. (i spent about 30 minutes trying so...). my approach for unit
tests in flex2 is currently to have a second entry point
(mx:Application) in my app and basically having 2 bowsers open, one
running my unit tests and
9 matches
Mail list logo
