From 4cee41d242e4c6d239305bb3abb50a23dee564a6 Mon Sep 17 00:00:00 2001
From: labkey-jeckels <jeckels@labkey.com>
Date: Thu, 18 Jan 2024 11:58:02 -0800
Subject: [PATCH] Support all labkey.xml/ROOT.xml settings via
 application.properties

---
 cluster/resources/web/cluster/htcondor/pipelineConfig.xml | 2 +-
 cluster/resources/web/cluster/slurm/pipelineConfig.xml    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/cluster/resources/web/cluster/htcondor/pipelineConfig.xml b/cluster/resources/web/cluster/htcondor/pipelineConfig.xml
index 44d6d328f..36f8e6c7a 100644
--- a/cluster/resources/web/cluster/htcondor/pipelineConfig.xml
+++ b/cluster/resources/web/cluster/htcondor/pipelineConfig.xml
@@ -3,7 +3,7 @@
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
 
-    <!--NOTE: if you plan to use ActiveMQ for status updates, you will need to configure this in labkey.xml-->
+    <!--NOTE: if you plan to use ActiveMQ for status updates, you will need to configure this in application.properties-->
 
     <bean id="pipelineJobService" class="org.labkey.pipeline.api.PipelineServiceImpl">
         <!--You will list all remote execution engines.  You will most likely only have one engine to register, but this example contains multiples to show different configurations-->
diff --git a/cluster/resources/web/cluster/slurm/pipelineConfig.xml b/cluster/resources/web/cluster/slurm/pipelineConfig.xml
index 4abf517c8..4c6c5e279 100644
--- a/cluster/resources/web/cluster/slurm/pipelineConfig.xml
+++ b/cluster/resources/web/cluster/slurm/pipelineConfig.xml
@@ -3,7 +3,7 @@
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
 
-    <!--NOTE: if you plan to use ActiveMQ for status updates, you will need to configure this in labkey.xml-->
+    <!--NOTE: if you plan to use ActiveMQ for status updates, you will need to configure this in application.properties-->
 
     <bean id="pipelineJobService" class="org.labkey.pipeline.api.PipelineServiceImpl">
         <!--You will list all remote execution engines.  You will most likely only have one engine to register, but this example contains multiples to show different configurations-->