Work around loplugin:oncevar with --disable-dbgutil

Change-Id: I8f2a2910993609dec91e63074a5b9195a2352bb5

extensions/source/abpilot/fieldmappingimpl.cxx

@@ -229,13 +229,13 @@ namespace abp
 
             for ( ; pExistentFields != pExistentFieldsEnd; ++pExistentFields )
             {
-#ifdef DBG_UTIL
-                OUString sRedundantProgrammaticName;
-                aFields.openNode( *pExistentFields ).getNodeValue( sProgrammaticNodeName ) >>= sRedundantProgrammaticName;
-                DBG_ASSERT( sRedundantProgrammaticName == *pExistentFields,
-                    "fieldmapping::writeTemplateAddressFieldMapping: inconsistent config data!" );
+                SAL_WARN_IF(
+                    ((aFields.openNode(*pExistentFields)
+                      .getNodeValue(sProgrammaticNodeName).get<OUString>())
+                     != *pExistentFields),
+                    "extensions.abpilot",
+                    "fieldmapping::writeTemplateAddressFieldMapping: inconsistent config data!");
                     // there should be a redundancy in the config data .... if this asserts, there isn't anymore!
-#endif
 
                 // do we have a new alias for the programmatic?
                 MapString2String::iterator aPos = aFieldAssignment.find( *pExistentFields );

include/sal/log-areas.dox

@@ -174,6 +174,7 @@ certain functionality.
 
 @section extensions
 
+@li @c extensions.abpilot
 @li @c extensions.biblio
 @li @c extensions.dbpilots
 @li @c extensions.plugin