Hi folks,
I'd like to feel your temperature wrt the following improvement I would
like to make to Maven before I start working on it.
*== Artifact-based Reposi**tories* ==
In Tycho we have these constructs:
https://wiki.eclipse.org/Tycho/Reference_Card#Repository_providing_the_context_of_the_build
<repository>
<id>eclipse-indigo</id>
<layout>p2</layout>
<url>http://download.eclipse.org/releases/indigo</url>
</repository>
P2 repositories can be encapsulated in an archive. An archive,
naturally, can be available as an artifact in some repo somewhere
(including the local one).
What would you think about adding something like:
<repository>
<id>eclipse-indigo</id>
<layout>p2</layout>
<groupId>foo</artifactId>
<artifactId>bar</artifactId>
<version>1.2.3-SNAPSHOT</version>
<type>tgz</type>
<required>true</required>
</repository>
The broad strokes are as follows:
* Repo artifact becomes a dependency of an artifact being built on the
same terms as its parent would be, i.e. if you can't find parent you
can't build same with repo artifact (by default)
* If repo <required> (or <optional> to reverse the semantics) is false
(true), failure to resolve the repository does not lead to a
critical failure and reactor proceeeds as if the repository
declaration did not occur.
* Repo artifact is attempted to be resolved using all of the
repositories inherited from parents, ad infinitum, or in the
repository declarations prior to the one being considered. Artifact
is, otherwise, resolved by standard means.
Let me know what you think,
--
Arcadiy Ivanov
[email protected] | @arcivanov | https://ivanov.biz
https://github.com/arcivanov
