> From: Chris Burke <[email protected]> > > Oleg Kobchenko wrote: > > Another approach is have one project.ijp and have different targets in it > > for build, test, run, etc. > > > > Also for situation like "test", one may do without a target, but instead > > having a naming convention like test.ijs, and a common harness to run it, > > rather than duplicating the harnesses from project to project like it is > > done now. > > Yes, this is equally possible. It just means that build.ijs, test.ijs, > run.ijs are special scripts within a project. I don't mind this > approach, as it is essentially what I do right now - the only difference > being that these names would be automatically used by a project, instead > of having to be defined manually. Of course, you could then not create a > project whose source scripts included one of build.ijs, test.ijs etc.
"test.ijs" is THE tests themselves--the numerous little verbs with asserts, not the harness. There aren't no "build.ijs or run.ijs etc-- these targets are defined in the project file (whichever the extension). A target is either declaratively defined (no code or code in common harness of the PM API), or consists of a single verb which has the action-sentences. Bill is right, the project file is very similar to a Makefile. For an example of a project with multiple targets see http://www.jsoftware.com/pipermail/beta/2009-October/003352.html The idea of such a project with multiple targets is similar to http://www.jsoftware.com/jwiki/Addons/general/unittest See also http://www.jsoftware.com/pipermail/beta/2009-October/003349.html http://www.jsoftware.com/pipermail/beta/2009-October/003344.html http://www.jsoftware.com/pipermail/beta/2009-October/003315.html ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
