On 25/05/2010 19:34, George Stan (JIRA) wrote: > 2. Click catches allot of problems and it's doing allot of checks at runtime, > but they consume quite a few cycles. > What if those checks would be "configurable"/ optional at runtime (so would > consume no resources/cycles at all if turned off), but instead they would be > as Checkstyle based tasks, that the user can perform at build time? > In performance intensive installations this could be a fantastic improvement.
Could you share some of the checks you are referring to? When you say fantastic performance gains are we talking orders of magnitude? Do you have profiled data we could look at to see some of the bottlenecks? Kind regards Bob
