original submission:

> Let's have a project with a cluster in a subdirectory "src" and an ACE file referencing that cluster by a relative path.
>
> cluster
>   my_app: "./src"
>
> if `se c` or `se doc` is called from a directory different from the directory where the ACE file is located, the relative path is resolved relative to the current working directory and the cluster is not found. (`se c` crashes on missing classes, `se doc` prints a warning and generates documentation without the unfortunate cluster.) Wouldn't it make more sense to use directory of the ACE file as base for relative path resolution?

Yes indeed.
 

> How I ran into this: `se doc` saves documentation in the current working directory, but I wanted to generate it in a separate place, not in the project root.

A possible workaround is to provide an "--output a_directory" option. At a first glance it may avoid the occurrence of the bug.