Chicken Wing Posted September 15, 2015 Author Share Posted September 15, 2015 Yes, the other Tasks having different constructors could have caused the problem. If one of those tasks had higher priority in the classpath than the Task you wanted (assuming they were both loaded in for some reason), you would get that error, since they do not contain the constructor you want (instead, they contain one for a different script) Ah I see, so at run time the Task class had a different signature, I thought I was something to do with the classpath, oh well, thanks for the help Quote Link to comment Share on other sites More sharing options...
