add support for Ant

[danglotb]

Support Ant project such as Maven or Gradle project.

[danielleberre]

Yep, that would be very useful for me, thanks 👍

[danzone]

Hi all, I assigned it to myself in order to plan with ENG team the development.

[monperrus]

Thanks!

[danzone]

Hi @danglotb, @monperrus , do you prefer to have dspot-ant as a separated project within STAMP-project folder, or to have it as a sub-folder within STAMP-project/dspot folder? My concern is about mixing Maven modules and not-Maven modules in the same place. Theoretically, the root pom.xml file lists explicitly sub-modules, so having a non-Maven project wouldn't hurt. Please let me know what do you prefer. But having dspot-ant project in a different place would make more clean the dspot project folder structure. Incidentally we will have to take a similar decision when the DSpot Gradle plugin development will start.

[danglotb]

Hi @danzone

Thank you for developing the support of Ant project.

The issue here, is about to have the implementation of an AutomaticBuilder such as the GradleAutomaticBuilder you did and the MavenAutomaticBuilder that I did but for Ant project.

In this case, I don't understand the point to create a sub-folder or module in DSpot.

We need the implementation of Ant task in a AntAutomaticBuilder and update entry point (options and main classes) to support it, right?

[danzone]

Hi @danglotb, good point, I was reasoning in a black-box way (the Ant task calls DSpot passing all parameters), and I didn't consider to build some kind of AntAutomaticBuilder. Things got complicated here (not so much indeed): I will add an activity to develop the AntAutomaticBuilder. Regarding the point of having a sub-folder (not a sub-module, it wouldn't make sense) is simply a matter of taste: do you prefer to have the DSpot Ant Task project within STAMP-project/dspot folder, or outside it?

[danzone]

Sorry @danglotb , I took for granted that the Ant Task was a... Ant project itself, but it's more preferable to set-up a Maven project to develop the Ant Task, so you can ignore my last question. The activity will be performed with the following tasks:

1. develop the AntAutomticaBuilder
2. develop the Ant Task to use it within Ant project.
   In this way we can publish the Ant Task within a Maven repository, and it could be also used along with Apache Ivy as a dependency manager for Ant tasks.

[monperrus]

That would be super cool to have this, so that OW2 project SAT4J (@danielleberre ) can be used as case study for Dspot