On 2015-03-21 09:37, Karl Heinz Marbaise wrote:
Hi,
On 3/21/15 2:14 PM, Arcadiy Ivanov wrote:
So Maven pom is set in stone and no changes can be introduced to it?
For Model version 4.0.0 at which is Maven at the moment i don't see a
chance for such things...
But there is no thing which prevents us from changing for Maven Model
5.0.0 (Maven 4.X)...
[...]
It breaks cause the tags are not optional....
I have simply added a repository like you suggested to an existing pom
which results in the following:
[...]
What would be the fundamental reason for never ever ever considering any
additions to the POM ever again?
The problem is compatibility and the toolchain which already exist and
would break..
It is absolutely true that if this feature is introduced Maven less than
version X will not accept the POM. But Maven ver X+ will still accept
both URL-based and Artifact-based repositories. Hence the forward
compatibility, not backwards. Maven already has prerequisites
.
See here: Many ideas already exist...
http://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
In particular the part: "Issues to be reviewed for 4.x"...
You could make a entry with your suggestins etc. and maybe a proof of
concept implementation?
That's great! Thanks a lot, I'll do that.
On 2015-03-21 04:11, Jeff MAURY wrote:
then your stuff will not be Maven compatible. You will face non
adoption
from the community
Jeff
On Sat, Mar 21, 2015 at 9:01 AM, Arcadiy Ivanov <[email protected]>
wrote:
Presumably, by editing maven-model/src/main/mdo/maven.mdo ? :)
On 2015-03-21 03:31, Jeff MAURY wrote:
how will you extend the repository element in maven ?
Jeff
On Fri, Mar 20, 2015 at 11:52 PM, Arcadiy Ivanov <[email protected]>
wrote:
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
--
Arcadiy Ivanov
[email protected] | @arcivanov | https://ivanov.biz
https://github.com/arcivanov
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Arcadiy Ivanov
[email protected] | @arcivanov | https://ivanov.biz
https://github.com/arcivanov
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
