Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-1706

policy/engine mvn clean install leaves residue in the repository

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Dublin Release
    • Dublin Release
    • None
    • None

      After doing a mvn clean install, one file is modified while others are not cleaned up. This is not good software practice. Now when developers need to rebase they have to pull the head version of xacml.properties and git clean -fd the directory.

      Changes not staged for commit:

        (use "git add <file>..." to update what will be committed)

        (use "git checkout – <file>..." to discard changes in working directory)

       

      modified:   ONAP-PAP-REST/src/test/resources/pdps/xacml.properties

       

      Untracked files:

        (use "git add <file>..." to include in what will be committed)

       

      ONAP-PAP-REST/src/test/resources/pdps/1/

      ONAP-PAP-REST/src/test/resources/pdps/testgrp1/

      ONAP-PAP-REST/src/test/resources/pdps/testgrp2/

      ONAP-PAP-REST/src/test/resources/pdps/testgrp4/

      ONAP-PAP-REST/src/test/resources/pdps/testgrp5/

      PolicyEngineUtils/sql/

      PolicyEngineUtils/src/test/resources/META-INF/generatedCreate.ddl

      PolicyEngineUtils/src/test/resources/META-INF/generatedDrop.ddl

       

      Please change the JUnit tests so that they do not modify test files:

      ONAP-PAP-REST/src/test/resources/pdps/xacml.properties

      and cleanup the src/test/resources.

       

      Suggestion is to use JUnit temporary folder.

       

            pa834y pa834y
            pdragosh pdragosh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: