@@ -6,9 +6,9 @@ This guide covers common issues you may encounter when using RAP Builder and how
66
77Before diving into specific issues, try these steps:
88
9- 1 . ** Enable verbose logging** to see detailed output:
9+ 1 . ** Enable debug logging** to see detailed output:
1010 ``` powershell
11- relsvr-rap build ... --log-level Verbose --log-file logs/debug.log
11+ relsvr-rap build ... --log-level Debug --log-file logs/debug.log
1212 ```
1313
14142 . ** Review the log file** in the ` RAPBuilderLogs/ ` directory (or your custom location).
@@ -41,7 +41,7 @@ Before diving into specific issues, try these steps:
4141
42423 . Check file system permissions on the output directory.
4343
44- 4 . Enable verbose logging to see what happened:
44+ 4 . Enable debug logging to see what happened:
4545
4646### Exit Code 1
4747
@@ -181,7 +181,7 @@ Failed to parse build.xml: Invalid XML format
181181
182182** Solutions:**
183183
184- 1 . Validate your XML files with an XML validator or use ` --log-level Verbose ` to see parsing details.
184+ 1 . Validate your XML files with an XML validator or use ` --log-level Debug ` to see parsing details.
185185
1861862 . Check for common XML issues:
187187 - Missing closing tags (e.g., ` <Assembly> ` without ` </Assembly> ` )
@@ -267,6 +267,6 @@ relsvr-rap : The term 'relsvr-rap' is not recognized as the name of a cmdlet, fu
267267
268268If you cannot resolve an issue using this guide:
269269
270- 1 . Run the build with ` --log-level Verbose ` and review the full log output.
270+ 1 . Run the build with ` --log-level Debug ` and review the full log output.
2712712 . Verify your ` build.xml ` and ` application.xml ` against the [ Configuration Reference] ( configuration-reference.md ) .
2722723 . Contact Relativity developer support with your log file and configuration files.
0 commit comments