diff --git a/src/addon/NUOPC/doc/NUOPC_StandardComponentDep.tex b/src/addon/NUOPC/doc/NUOPC_StandardComponentDep.tex
index 4751aeed12..898ff1d86f 100644
--- a/src/addon/NUOPC/doc/NUOPC_StandardComponentDep.tex
+++ b/src/addon/NUOPC/doc/NUOPC_StandardComponentDep.tex
@@ -2,6 +2,8 @@
 
 \label{componentDep}
 
+{\bf DEPRECATION NOTICE:} The mechanism described in this section for defining build dependencies between components has been deprecated! The approach discussed here is based exclusively on GNU Makefiles. It has been superseded by the functionality implemented in the \htmladdnormallink{ESMX Layer}{http://earthsystemmodeling.org/esmx/}. The ESMX approach addresses all of the issues discussed here, but represents are more holistic solution. It includes a standard CMake based option, which is the recommended approach for all new NUOPC projects.
+
 Most of the NUOPC Layer deals with specifying the interaction between ESMF components within a running ESMF application. ESMF provides several mechanisms of how an application can be made up of individual Components. This chapter deals with reigning in the many options supported by ESMF and setting up a standard way for assembling NUOPC compliant components into a working application.
 
 ESMF supports single executable as well as some forms of multiple executable applications. Currently the NUOPC Layer only addresses the case of single executable applications. While it is generally true that executing single executable applications is easier and more widely supported than executing multiple executable applications, building a single executable from multiple components can be challenging. This is especially true when the individual components are supplied by different groups, and the assembly of the final application happens apart from the component development. The purpose of standardizing component dependencies as part of the NUOPC Layer is to provide a solution to the technical aspect of assembling applications built from NUOPC compliant components.