bugLiberty Eiffel - Bugs: bug #65307, ACE file: relative paths resolved...

 
 

bug #65307: ACE file: relative paths resolved as relative to the cwd

Submitter:  Jakub Pavlík <igneus>
Submitted:  Tue 13 Feb 2024 05:42:55 PM UTC
   
 
Category:  Liberty tools Severity:  3 - Normal
Priority:  * 5 - Normal Status:  Confirmed
Assigned to:  None Open/Closed:  Open
Release:  None Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 17 Feb 2024 10:38:19 PM UTC, comment #1: 


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.

Paolo Redaelli <Tybor>
Group administrator
Tue 13 Feb 2024 05:42:55 PM UTC, 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?

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.

$ mkdir doc
$ cd doc
$ se doc ../my_app.ace

... but then the application classes didn't show up in the documentation.

Jakub Pavlík <igneus>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Tybor (Posted a comment)
  • -email is unavailable- added by igneus (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-02-17 Tybor StatusNone Confirmed

    Back to the top

    Powered by Savane 3.13-6ae7.
    Corresponding source code