MohanTS

Get Maven JARs without Maven

For Ant builds, legacy projects, and no-build setups — paste your dependencies, get a ZIP.

No data retention Transitive resolution One-click ZIP
1
Paste one or more <dependency> XML blocks
→
2
Resolve the full transitive tree
→
3
Download all JARs as ZIP
Maven Dependencies XML
Paste your Maven dependencies list in XML format below

Who is this for?

A
Ant projects
Maintaining or migrating legacy Java apps? Drop the JARs into your lib/ folder and reference them in build.xml.
N
No-build projects
Just need JARs on a classpath without setting up a full Maven or Gradle project? Paste, resolve, download.
O
Offline environments
No repository access at runtime? Download once, use everywhere. Perfect for air-gapped or restricted networks.
P
Quick prototyping
Spinning up a quick proof-of-concept? Grab the JARs you need in seconds — no project setup required.

Why use this?

1
No Maven needed
Works entirely in your browser. No mvn, no pom.xml project, no JDK required on your machine.
2
Transitive resolution
Automatically fetches the full dependency tree — you only paste the top-level dependencies, we resolve the rest.
3
Conflict resolution
Handles version conflicts intelligently using nearest-wins semantics, just like Maven would.
4
One-click ZIP
All JARs bundled into a single ZIP. Extract, add to classpath, and you're done.
Ant build.xml — use the downloaded JARs:
<path id="classpath">
    <fileset dir="lib" includes="**/*.jar"/>
</path>

<javac srcdir="src" destdir="build">
    <classpath refid="classpath"/>
</javac>

FAQ

Is my data stored?
No. Everything runs client-side in your browser. Your dependency XML is never sent to a server or stored anywhere.
Does it support Maven Central only?
Yes, currently all dependencies are resolved from Maven Central. Support for additional repositories may be added in the future.
How are version conflicts resolved?
Version conflicts are resolved using nearest-wins semantics, the same approach Maven uses in its dependency mediation.
Can I use this without a POM file?
Yes. You don't need a full pom.xml — just paste individual <dependency> blocks and the tool will resolve them.
What about POM-packaging dependencies?
POM-type dependencies are resolved for their transitive metadata but only JAR artifacts are included in the downloaded ZIP.