Keep project-specific rules directly in project directory

Author: FloBoJa

.github/workflows/reverse_engineering.yml

@@ -81,9 +81,8 @@ jobs:
           echo "current_version=$(yq eval '.current_version' $CONFIG_FILE)" >> $GITHUB_ENV
           echo "rules=$(yq eval '.rules[]' $CONFIG_FILE | paste -sd ",")" >> $GITHUB_ENV
 
-          RULES_PATH=$(yq eval '.rules_path // ""' $CONFIG_FILE)
-          if [ -n "$RULES_PATH" ]; then
-            echo "rules_path=benchmark/${{ matrix.directory }}/$RULES_PATH" >> $GITHUB_ENV
+          if [ -f benchmark/${{ matrix.directory }}/ProjectSpecificRules.xtend" ]; then
+            echo "rules_path=benchmark/${{ matrix.directory }}" >> $GITHUB_ENV
           else
             echo "rules_path=" >> $GITHUB_ENV
           fi

descartesresearch-teastore-psr/.retriever.yml

@@ -4,4 +4,3 @@ rules:
   - org.palladiosimulator.retriever.extraction.rules.maven
   - org.palladiosimulator.retriever.extraction.rules.jax_rs
   - org.palladiosimulator.retriever.extraction.rules.ecmascript
-rules_path: rules

descartesresearch-teastore-psr/rules/ProjectSpecificRules.xtend renamed to descartesresearch-teastore-psr/ProjectSpecificRules.xtend

@@ -4,4 +4,3 @@ rules:
   - org.palladiosimulator.retriever.extraction.rules.gradle
   - org.palladiosimulator.retriever.extraction.rules.jax_rs
   - org.palladiosimulator.retriever.extraction.rules.ecmascript
-rules_path: rules