> From: Chris Burke <[email protected]> > > One slight awkwardness with the project manager is the name of the > project file itself, and the associated files for test and build. The > .ijp extension is used only for projects, though it is an ordinary > script file; while the test and build scripts cannot be distinguished > from other scripts in the project. In each case, any name can be chosen > for each of the files. > > I suggest that the project extension be used for each of these files and > that the names be fixed. Specifically, project.ijp will be the project > configuration, test.ijp and build.ijp the test and build scripts. > Perhaps also run.ijp for a run script different from test. > > Here the .ijp extension is re-used, since there is likely to be a > one-off conversion, and there is not much chance anyway of conflict - > but this is not really important, and another extension could be used. >
> From: Chris Burke <[email protected]> > > bill lam wrote: > > Did you mean project.ijp will be used for loading scripts in that > > project? > > It would be the project configuration file, same as the current xxx.ijp > file except with updated definitions. 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. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
