Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

Mercury is a serious attempt to:

<ul>
	<li>Decouple major Maven components, making them available as stand-alone building blocks rather then having Maven as as one big monolith, not usable outside of its environment.</li>
	<li>Artifact - clearly separate an Artifact from its metadata.</li>
	<li>Repository - convert a repository into active component. It used to give back just pathOf(), now it accepts GAV collections and gives back either metadata or full blown Artifacts.</li>
	<li>Transport - an API in development.</li>
	<li>DependencyBuilder main API for dependency graph creation and conflict resolution.</li>
	<li>Decouple container, so that these components are just plain pojos. This is not necessarily good as wiring components together without a container complicates using the library.</li>
	<li>Introduce Jetty-based HTTP/HTTPS and WebDAV transactional transport layer.</li>
	<li>Asynchronous downloads and uploads. One of the few successful usages of Java NIO in OSS.</li>
	<li>Transactional operations - all-or-nothing for file sets.</li>
	<li>Move integrity control into transport layer, upper level components should not care about these details.</li>
	<li>Abstract out metadata cache, provide at least one implementation there.</li>
	<li>Integrate these changes back to Maven 3.x to make it even better platform than it is right now</li>
</ul>

Currently Mercury can already be used for accessing repositories, and conflict resolution/classpath calculation.