Skip to content

Commit 3da0dfe

Browse files
Jamesclaude
authored andcommitted
Fix unparseable pom.xml: -- is not allowed inside an XML comment
The previous commit put "-- which is how" inside a <!-- --> block, which XML forbids, so pom.xml stopped parsing and all three CI jobs failed, Linux included. It was pushed because the local check could not see it. The verification was mvn -q clean test 2>&1 | grep -E "^Tests run:|BUILD FAIL" | tail -1 and the actual error is "Non-parseable POM", which matches neither pattern. The grep printed nothing, and nothing read as success. A filter that silently passes on an unmatched failure is not a check. Verified here on the exit code instead, with the POMs and the workflow YAML parsed explicitly. mvn clean package -DskipTests: exit 0. mvn clean test: 144 tests, the same 3 known analyzespTest failures. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012qPRpoD8exYRrUmbfXXWXj
1 parent c34872e commit 3da0dfe

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

pom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@
227227
redefined myMetaDB / TInfoRecord / SortIgnoreCase,
228228
which the retained TGetTableColumn.java in the same
229229
package already provides, so it also broke any
230-
wildcard compile of that folder -- which is how
230+
wildcard compile of that folder, which is how
231231
compile_gettablecolumns.bat compiles it. Deleted. -->
232232
<exclude>gudusoft/gsqlparser/demos/columninspect/ColumnInspect.java</exclude>
233233
<exclude>gudusoft/gsqlparser/demos/dlineage/DataFlowAnalyzer.java</exclude>

0 commit comments

Comments
 (0)