The reason is, that already a date class is provided in the ivy script environement. If you import another date class, there will be an error: "The import java.util.Date collides with Date". We provide some utility classes from the package `ch.ivyteam.ivy.scripting.objects` like `Date`, `Time`, `DateTime` which should be more intuitive to use than the regulary java classes from the jdk like `java.util.Date`. You can still use `java.util.Date` But you need to address the class with the fully qualified name. Like: `java.util.Date date = new java.util.Date();`. As you can think, some APIs requires `java.util.Date` as parameter and therefore its needed.

The reason is, that already a date class is provided in the ivy script environement. If you import another date class, there will be an error: "The import java.util.Date collides with Date". We provide some utility classes from the package `ch.ivyteam.ivy.scripting.objects` like `Date`, `Time`, `DateTime` which should be more intuitive to use than the regulary java classes from the jdk like `java.util.Date`.