On Sun, Jan 23, 2011 at 10:28 AM, Mathias Kalb <mathias.k...@prodato.de>wrote:
> Hi Hans, > > > >> 1. If a task which need dependencies (compileJava, >> compileJavaTest, test) has no input, then the resolving of the >> dependencies can be skipped. >> >> >> The classpath is an input to the compile task. A modified classpath is a >> trigger for a recompile. >> > Yes, but isn't is possible to check first, if a compile or run is > neccessary? Sorry. I should have read properly. Of course you are right. Hans > > > > > >> >> 2. If the dependencies are resolved for the compileJava tasks, >> then the result can be used for the compileJavaTest task. >> >> >> We can't reuse it necessarily. For example their might be a different >> version conflict resolution. >> > Yes, I know this problem, but I hoped that some informations can be cached > and reused. > > > >> 3. Enhance the profile report with the follwing two durations: >> Ivy/Maven/Dependency >> UP-TO-DATE check (reading, calculating, writing). >> >> >> Good idea. >> >> >> Okay, I will create an issue. > > regards, > Mathias Kalb > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
