The .nuspec, its OPC relationships and the Maven POM now parse with lineEndings normalize, as XML 1.0 section 2.11 and the NuGet and Maven readers do. Text from CRLF files no longer keeps carriage returns.
5.6 KiB
Maven POM and Gradle module metadata
inspect_maven_gradle_metadata / inspect-maven-gradle-metadata reports the
coordinates, dependency declarations, BOM or platform notes, and unresolved
property or parent references written in one selected local Maven pom.xml or
Gradle .module file. It reads the file without running Maven or Gradle,
resolving a dependency tree, or contacting a repository.
rea inspect-maven-gradle-metadata /absolute/path/to/pom.xml --json
rea inspect-maven-gradle-metadata /absolute/path/to/demo-1.2.3.module --json
The CLI resolves relative paths against the caller's working directory. MCP requires an absolute filesystem path and preserves that exact selection:
{
"name": "inspect_maven_gradle_metadata",
"arguments": { "path": "/artifacts/pom.xml" }
}
Classification is from content, not the suffix: a well-formed Maven <project>
document is maven-pom; a JSON object with formatVersion and a component
or variants array is gradle-module.
Observations
The inline Evidence result contains the artifact path, SHA-256, and byte length.
Its parameters retain caller-selected controls. An omitted max_file_bytes
uses the default for execution and stays out of the parameters; an explicitly
selected default remains recorded.
coordinates holds group_id, artifact_id, version, and packaging as
spelled. Missing project coordinates stay null. A ${property} spelling is
kept as written and listed in unresolved; this reader does not interpolate
properties or inherit parent or BOM values. POM text goes through XML
end-of-line handling, as Maven's reader applies it: CRLF and lone CR read as LF.
When a parent is declared, omitted project group/version fields point to the
parent as possible sources. An omitted project artifactId is a missing child
coordinate: only group/version coordinates may be inherited.
For a POM, parent records the declared parent coordinates and relative_path
when present. relative_path_declared distinguishes an empty <relativePath/>,
which disables Maven's local parent lookup, from an omitted tag. properties
lists each child of <properties> as name and value. URL userinfo
credentials in a property value are removed and value_credentials_redacted
is true; when the credential span cannot be located, value is null.
dependencies comes from the project's <dependencies> list.
dependency_management comes from <dependencyManagement>. A managed
dependency with type pom and scope import is a BOM import
(bom_import: true). Each row keeps scope, type, optional, classifier, and
exclusions as present. optional is the interpreted boolean and
optional_spelling keeps the text as written, so a ${property} value stays
visible and is listed in unresolved with field optional. version_kind
is literal, range, dynamic, property, or missing; dynamic is
Gradle's + prefix (1.+) or a latest.<status> selector
(latest.release).
For Gradle module metadata, gradle records format_version,
created_by_gradle, and each variant's name, org.gradle.category,
org.gradle.usage, available-at coordinates as spelled, and declared
dependency and constraint counts. Variant dependencies are origin
variant-dependencies; dependencyConstraints are origin
variant-constraints. Rich versions keep requires, prefers, strictly,
and rejects. A variant whose category is platform or enforced-platform
marks its constraints platform: true. available-at is not fetched. URL
userinfo credentials in available_at.url are removed and
url_credentials_redacted is true; when the credential span cannot be
located, url is null.
unresolved names every property reference in the coordinates, packaging, and
each dependency's scope, type, classifier, and optional, plus missing
coordinates that a parent would normally supply and other missing coordinates. These are explicit
unknowns, not guesses.
Limits and failures
The selected file is limited to 1 MiB by default (16 MiB maximum). Exceeding
the budget fails without partial success. Malformed XML or JSON is
invalid_format. A well-formed document that is not a Maven project or Gradle
module metadata file is unsupported_target. Document type declarations are
unsupported. External entities are not resolved.
A POM is counted as a stream before its document tree is built, and one with
more than 1,048,576 XML nodes (elements, attributes, text, CDATA, comments and
processing instructions) is refused as a resource limit, as is a report above
65,536 dependency and constraint rows, 4,096 Gradle variants, or 65,536
dependency exclusions summed over every row. Each collection is counted before
its report records are built.
Unresolved property-reference and coordinate-gap records share a 65,536-record
allowance. Repeated references within one field are deduplicated in source
order; the same spelling in different fields or rows remains separate evidence.
Variant names repeated across dependency and constraint rows are also limited
to 4,194,304 UTF-16 code units. These fixed parser and report allowances are
separate from the selected file-read budget; raising max_file_bytes does not
raise them.
POM profiles, when present, stay unread and unactivated. Declared repositories
stay unread and are not contacted. Packaging is not defaulted to jar when
omitted. Gradle variant attributes other than category and usage are not
decoded.
Complete coverage means the selected document was read. It does not establish a resolved dependency tree, a repository fetch, or that Maven or Gradle would select the same versions.