go>> lonae>> 返回
项目作者： vaccovecrana

项目描述 ：
A lightweight Maven dependency resolver
高级语言： Java
项目地址: git://github.com/vaccovecrana/lonae.git
创建时间： 2019-01-24T22:50:54Z
项目社区：https://github.com/vaccovecrana/lonae
开源协议：Apache License 2.0
下载


lonae

A lightweight Maven dependency resolver.

Overview

lonae allows you to resolve runtime dependency graphs for Maven artifacts and
repositories from within your client code.

Quick disclaimer: To make the best use of your time (and mine):

This project, although functional, is still in an experimental stage. If you
are expecting to get artifacts resolved in the exact same way Maven
or Gradle would, then lonae is not for you. At least not until solid
support for runtime dependency semantic quirks is established/implemented.

That said, lonae will try to make a reasonable choice of run-time artifact
selections based on a set of Maven coordinates that you provide.

NOTE: since “reasonable“ has a very broad interpretation, please be sure
to read these usage notes in their entirety.

Installation

Download

Add the following dependency from JCenter to your project:

  1. implementation "io.vacco.lonae:lonae:<VERSION>"

Usage

  1. MmRepository repo = new MmRepository("/tmp/repo", "https://repo1.maven.org/maven2/");
  3. List<MmResolutionResult> jars = repo.installDefaultFrom(MmCoordinates.from("org.apache.arrow:arrow-jdbc:0.12.0"));
  4. List<MmResolutionResult> sources = repo.installFrom(MmCoordinates.from("org.apache.arrow:arrow-jdbc:0.12.0"), "sources");

Motivation

So far, I have yet to find a minimalistic library which supports M2 artifact
resolution semantics. The libraries mentioned at the end of this document are
more specialized in execution scopes other than run-time. They also bring in
additional frameworks and dependencies of which I have very little
to no control of (as well as a deep understanding of, for better or worse).

Again, the purpose of lonae is completely focused on the runtime artifact
retrieval for an application.

What’s supported

  • Maven style runtime dependency detection and installation (with optional classifiers) into a local repository.
  • import scoped pom dependencies (to support multiple inheritance.
  • Gradle’s latest version wins default conflict resolution strategy.

What’s left to do (Pull Requests welcomed and encouraged).

  • Maven’s closest version wins default conflict resolution strategy.
  • Adding dependencies from default active profile.
  • Version range selectors.
  • LATEST version selector.
  • Maven deployment metadata for SNAPSHOT artifacts.
  • Artifact MD5/SHA checksum verification on downloaded artifacts.

A few recommendations:

  • Use fixed version numbers.
  • Try to publish uber-jar style shaded packages for larger applications (i.e.
    dependency resolution accuracy starts suffering once complex dependency trees
    are specified).

Similar projects

Disclaimer

This project is not production ready, and still requires security and code correctness audits.
You use this software at your own risk. Vaccove Crana, LLC., its affiliates and subsidiaries waive
any and all liability for any damages caused to you by your usage of this software.