IvySvn is a resolver for Ivy 2.0 which uses Subversion for storing artifacts for use in Ivy's publish and retrieve operations. Ivy is a dependency manager for Java which can be integrated into Ant builds to allow for retrieval of artifacts (e.g. third-party jar files) which your project may depend on as well as publication of artifacts (e.g. your own .jar/.war/.ear/.tgz files etc.) that your build generates. Subversion is not supported "out of the box" by Ivy itself, which is the gap that IvySvn aims to fill.

IvySvn can be downloaded here.

Please refer to the project's Wiki for usage and other information.

The key benefits of using IvySvn for existing Subversion users are:

Everything is in one place - your source code, dependent libraries and build artifacts are all kept in Subversion.
No need to set up and maintain a separate HTTP/FTP/etc. repository.
Ability to use Subversion's binary diff feature, reducing space required for multiple published versions of an artifact.
Ability to use Subversion revisions for retrieving artifacts, allowing more complex versioning.
Ability to publish artifacts to Subversion allows easy setup of dependencies between different projects in Subversion.
Less firewall and network configuration - can be used in environments where HTTP or other traffic is restricted but Subversion is allowed (e.g. build and testing machines).

If you have any issues, problems, queries, requests, comments or praise relating to IvySvn please send a message to the IvySvn group.

Note: IvySvn 2.1.0 requires >= Java 5.0.

Legal

This project is available under the Apache 2.0 License.

massdosage / ivysvn

readme

Legal