florath / rmtoo

Free and Open Source Requirements Management TooL
http://rmtoo.florath.net
Other
207 stars 59 forks source link

VCS control with git does not work (requirement file not found) #28

Open dav1d-wright opened 5 years ago

dav1d-wright commented 5 years ago

When I switch from filesystem access method to git, as described in the manpage rmtoo-config3 there seems to be some issue with the paths to the requirement files.

This is a snippet of my config file:

"topics": {
    "ts_common": {
    "sources": [
        [
        "git", {
            "start_vers": "f2dc410bb3cc7bec9c090d6c4f1433f092790058",
            "end_vers": "HEAD",
            "requirements_dirs": [ "requirements" ],
            "topics_dirs": [ "topics" ],
            "topic_root_node": "ReqSpec",
            "constraints_dirs": [ "constraints" ]}
    ] 

When I try to build the requirement spec, I get the following error:

make[1]: *** No rule to make target `doc/ReqSpec/requirements/project.req', needed by `artifacts/reqtopics.tex'.  Stop.

As soon as I switch from "git" to "filesystem" and remove "start_vers" and "end_vers" it works as desired. Does rmtoo have issues with the rmtoo project being located in a subfolder of the git repository?

Edit If I modify the "requirement_dirs" parameter in the Config.json file to represent the relative path to the git-root directoriy, it gives me the following error

+++ ERROR: Problem reading in the continuum [[ 108]: directory entry [doc] not found in tree [ReqSpec].]
florath commented 5 years ago

Can you please check, that the file project.req is available in the referenced versions?