Forum Discussion

koen_able's avatar
koen_able
Occasional Contributor
6 years ago

Composite project warning file has not been loaded

While running a SoapUI test in Jenkins I get the following warning:

16:52:51 16:52:51,093 WARN  [CompositeProjects] The file has not been loaded, because it is not specified in the project: /home/able/jenkins/workspace/REGRESSION_QCAUTO_0716/europort_test_automation/tooling-general/KeepAlive.xml

The file does not exist. It did exist before in Git, but it was removed and is not in Git anymore.

How do I get rid of this warning?

  • Hi koen_able,

     

    Could you please try the following solution posted here?

     

    WARN: The file has not been loaded, because it is not specified in the project: <file name>

    This message appears if the project directory contains .xml files that are not mentioned in the project.content file. ReadyAPI does not load such files.

    The issue is typically caused by several users working on the same shared project using different versions of ReadyAPI. The project.content file was introduced in ReadyAPI version 2.4. If a user who has ReadyAPI 2.3 or earlier edits a project created in ReadyAPI 2.4 or later, the changes will not show up in 2.4 or later versions.

    To fix the issue, delete the project.content file from the project directory. ReadyAPI will generate a new one on project opening, which will list all the items.

    Note: ReadyAPI may include non-project .xml files in the recreated project.content file. You will have to remove them manually.

    To avoid the issue, use the same version of ReadyAPI in your team.

  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)

    Hi koen_able,

     

    Could you please try the following solution posted here?

     

    WARN: The file has not been loaded, because it is not specified in the project: <file name>

    This message appears if the project directory contains .xml files that are not mentioned in the project.content file. ReadyAPI does not load such files.

    The issue is typically caused by several users working on the same shared project using different versions of ReadyAPI. The project.content file was introduced in ReadyAPI version 2.4. If a user who has ReadyAPI 2.3 or earlier edits a project created in ReadyAPI 2.4 or later, the changes will not show up in 2.4 or later versions.

    To fix the issue, delete the project.content file from the project directory. ReadyAPI will generate a new one on project opening, which will list all the items.

    Note: ReadyAPI may include non-project .xml files in the recreated project.content file. You will have to remove them manually.

    To avoid the issue, use the same version of ReadyAPI in your team.