I've managed to develop the Ant script that compiles all the modules/projects on Linux, but there is an annoying thing that happens, when different modules are compiled all the super classes are compiled also and local r files are created with folder structure from the super classes in the module.
For example if the Backend project is compiled folder structure and r files will be created in the project from the superclasses and those are in different project, can this be avoided somehow?
I've managed to develop the Ant script that compiles all the modules/projects on Linux, but there is an annoying thing that happens, when different modules are compiled all the super classes are compiled also and local r files are created with folder structure
from the super classes in the module.
For example if the Backend project is compiled folder structure and r files will be created in the project from the superclasses and those are in different project, can this be avoided somehow?
Flag this post as spam/abuse.
Mike is right, you'll need to have the rcode of parent classes referenced in your propath.
I am working on the same project as the original poster.
In some cases we have the r-code in a pl. But we also need to reference includes in the other projects, so these projects are still in the propath, albeit after the pl file.
Yet the behaviour persists. If the r-code is encountered much sooner in the propath (inb the pl file) than the source of the super classes, why are the super classes still compiled?
An alternative would be to make a project with the sole purpose to contain the include files with dataset definitions etc., but I really hate that idea, because that means that we must either mix up stuff from different projects in one place (which we wantto avoid, hence the different project) or double up on all projects.