How to convert json to a maven pom.xml file
- Step 1Structure the JSON as a POM definition — Include a top-level groupId, artifactId, version, and a dependencies array. Each dependency object needs groupId, artifactId, and version. Scope is optional and defaults to compile if omitted.
- Step 2Add properties and plugin config — Include a properties object for version constants and a build.plugins array for Maven plugin declarations. Each plugin object takes groupId, artifactId, version, and an optional configuration object.
- Step 3Convert and review the output XML — The output is a complete pom.xml with the standard Maven 4.0.0 schema. Review dependency scopes and verify groupId values match your Maven Central or Nexus repository coordinates.
- Step 4Replace or merge into your project — Copy the output into your project root as pom.xml, or selectively merge only the <dependencies> block into an existing POM using your IDE's XML merge or diff tool.
Frequently asked questions
Can I generate a multi-module parent POM?+
Yes. Include a modules array in the top-level JSON with each module directory name as a string. The output includes a <modules> block in the parent POM. Convert each child module's own dependency list separately to generate its module-level pom.xml.
How do I add Maven plugin execution configuration?+
Add a build.plugins array where each plugin object includes groupId, artifactId, version, and an optional executions array. Each execution can have an id, phase, goals array, and configuration object. The converter maps nested configuration keys as XML child elements inside the <configuration> block.
Is the dependency list uploaded to JAD Apps?+
No. The XML generation runs entirely in your browser. Your internal artifact versions, private repository coordinates, and project metadata are never sent to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.