An ant task would make CLOPS easier to use. The task should fail if there are any errors during generation. This requires some changes to the code too, to make sure that exceptions are not merely caught and reported.
I forgot to say how it works now. If clops-VER.jar and its dependencies are copied in $ANT_HOME/lib (/usr/share/ant/lib on ubuntu) then the following build.xml works:
<project default="foo" xmlns:clops="antlib:ie.ucd.clops.ant">
<target name="foo">
<clops:generate input="foo.clo">
</clops:generate></target>
</project>
Here "clops" is some shorthand that the user is free to choose.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A simple implementation is now committed.
I forgot to say how it works now. If clops-VER.jar and its dependencies are copied in $ANT_HOME/lib (/usr/share/ant/lib on ubuntu) then the following build.xml works:
<project default="foo" xmlns:clops="antlib:ie.ucd.clops.ant">
<target name="foo">
<clops:generate input="foo.clo">
</clops:generate></target>
</project>
Here "clops" is some shorthand that the user is free to choose.