[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aether-users] Guide to writing an aether provider
|
Bk Lau wrote:
I was trying to use aether as a farcade to an in-house non-maven artifact
repo by wrapping it.
Is this possible?. Or it has to be a maven-like repo?
I still have no clear understanding what your in-house non-maven repo
looks like and what differences you try to bridge. From your response to
my suggestion of a custom layout, I assume the differences are more
fundamental than just artifact paths.
There are two potential approaches depending on your exact requirements:
a) Custom RepositoryConnectorFactory
A repository connector gets artifacts and metadata from a remote
repository. The connector is fully responsible for what bytes will be
stored locally for the requested artifact/metadata. As such a connector
has the power to apply transformations to the repository contents, e.g.
synthesize a Maven POM from whatever the remote repository natively uses
to describe artifacts, similar for maven-metadata.xml.
This approach would be suitable if you still would like to use the
maven-aether-provider and interact with other, Maven-style repositories.
The aether-connector-basic is the example to take inspiration from.
b) Custom ArtifactDescriptorReader, VersionResolver,
VersionRangeResolver, MetadataGeneratorFactory
If you don't need interoperability with Maven repositories and rather
just would like to use the native metadata format of your in-house repo
for local operations, you would replace the maven-aether-provider with
your own impl of the components it provides.
Benjamin