Hi Alex, it doesn't show anything ... I just gave my JProfiler a spin at the problem and it seems that 100% of the time is spent in the following method: 100,0% - 95.868 ms - 1 inv. org.apache.flex.forks.velocity.Template.merge I'll do another run in a few minutes without enabling the default Filters, that strip out core Classes from the instrumentation.
Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:[email protected]] Gesendet: Samstag, 5. Oktober 2013 20:08 An: [email protected]; [email protected] Betreff: Re: Build times after switching to Apache Flex 4.10 What does the console say when hung? Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. [email protected] wrote: Hi, I invested quite some time to update my projects to using Flexmojos 6.0.1 and Apache Flex 4.10. I have to admit, that even if I created the Mavenizer and updated Flexmojos to work with them, I never used my own stuff in production yet ;-). I was using 4-x-beta with Flex 4.5.1 for my production projects, cause I didn't want to change a running system ... the switch seems to have been easy and successful. The only thing I noticed, is that while all modules have a similar build-times, all skin modules have an extremely increased build time (about 8 times of the older version) the Build seems to hang for 1-2 minutes until I can read the next line on the console ... does anyone have an Idea why this could be the case? Chris
